| Age | Commit message (Collapse) | Author |
|---|
|
this might need to be revisted later if its clear that there are machines
which only come up with a single state but more may appear after a PPC
change but for now we will just not initilize on systems with a single
state a boot. Solves a divide by zero panic when using the PDC diff on
broken hardware.
ok marco@, krw@
|
|
as well, reminded by miod@
|
|
ok oga@
|
|
caused the PIC to not be initialized on resume, which caused much
badness - things attached to the ISA bus weren't getting any
interupts (for example, keyboards).
Also move around some of the lapic reinit code to handle some clock
initialization bits we weren't doing before.
Worked out by deraadt and myself.
ok deraadt@
|
|
These values were used to eventually pass ranges to uvm_pglistalloc(),
which has been fixed to correctly skip no-memory ranges a lot of time ago;
however mvme68k would still use the computed range and osiop would no
longer attach; this repairs it.
|
|
eventually be needed by bouncebuffers, and I need it for some of my evil
graphics shitz.
ok kettenis@ with some tweaks
|
|
system.
This is needed in the case where you need managed pages so you can
handle faulting and pmap_page_protect() on said pages when you manage
memory in such regions (i'm looking at you, graphics cards).
these pages are flagged PG_DEV, and shall never be on the freelists,
assert this. behaviour remains unchanged in the non-device case,
specifically for all archs currently in the tree we panic if called
after bootstrap.
ok art@, kettenis@, ariane@, beck@.
|
|
in the IPI handler so that it works when it interrupts userspace,
waiting for the droppmap IPI to complete when destroying it, and
(most importantly) don't call pmap_tlb_droppmap() from cpu_exit().
Tested by myself and ckuethe, as our machines choked on the original.
ok @art
|
|
still support all different methods of getting states without e.g.
(highest/lowest state), and on i386 use the tables. The only change
should be the deletion of the mV from the printf at boot.
ok jsg@
|
|
work if it interrupts userspace
ok kettenis@ "you haven't committed that yet?" art@
|
|
IPIs are handled without blocking interrupts. This solves the random lockups
people have been seeing with apmd -C, thanks to marco@ for showing me how
to reliably recreate this hang, and claudio@ for telling me it was also
affecting his Athlon64 machine so I stopped chasing bugs in est.
ok oga@, weingart@
|
|
immediately when biglock wasn't held. But there is nothing inherently
wrong with doing copyin/copyout faults without holding biglock, so
just remove the check because it prevent us from doing copyin in
syscall before we grab the biglock.
|
|
aperture, which will take your memory, bind it to agp, and return you the
aperture address. It's essentially the same as iommu on amd64 in the way it
works.
This will be used by the upcoming (works but is slow and will not be
enabled at first) drm memory management code for intel igp chipsets.
Right now the sync function for intagp is really slow (doing a wbinvd()
on every sync), this is in the process of getting fixed, but the size of
the diffs in my trees was getting silly.
|
|
now this builds
|
|
|
|
information in files.conf like it should be.
|
|
|
|
|
|
Tested on multiple i386 and it works, amd64 works also with a few
exceptions that will get fixed.
The initial effort of importing was done by oga@, thanks!
Lots of testing and debugging by mlarkin@ and me.
Okay deraadt@, oga@, mlarkin@.
|
|
that wasn't needed.
ok pirofti@
|
|
(Allows time to flow forward after resume)
ok pirofti@
|
|
|
|
|
|
|
|
|
|
but even with proposed fixes, the reaper panics are back.
|
|
|
|
|
|
X driver for this chip doesn't know how to clean up after itself.
|
|
still do the right thing if the MBR has a lie in it
|
|
properly. Now i386 and amd64 implementations match.
ok art
|
|
ok art
|
|
|
|
|
|
|
|
bounds information, ie. the zone of the disk that OpenBSD can use. Have each
pre-disklabel parser (MBR, DPME, or per-arch MD disklabel parsers) figure out
this area and pass it up to userland. Then, delete all the same disk parsing
code from disklabel(8) since the kernel passes it up. Lots and lots of - signs
in the disklabel(8) code.
Tested on as many platforms as possible, the fallout will be repaired as time
goes on. To test, use disklabel -d <drive> and validate that the bounds do not
overlap any boot blocks. This same information is used by disklabel -A...
OK for the concept from krw, miod, and drahn
|
|
|
|
by anything.
|
|
Noticed by & ok deraadt@
|
|
|
|
|
|
|
|
3D Labs Permedia 2v chip. These cards were sold by Sun as PGX32.
|
|
3D Labs Permedia 2v chip. These cards were sold by Sun as PGX32.
|
|
size on a running system.
ok art@, oga@
|
|
ok miod@
|
|
|
|
ok miod@
|
|
arches. ok todd@ beck@
|
|
Okay jordan@ and marco@.
|
