| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
802.11n USB devices.
These are FullMAC devices that require a firmware to operate;
see man page for details.
Great thanks to Brad for donating hardware.
Committed over the TRENDnet TEW-649UB.
ok deraadt@
|
|
were dropped.
|
|
of the non-equivalent aliases for it.
ok miod@
|
|
one bad case of use-after-free after a hell lot of heavy I/O creeping in again
in this driver. This doesn't fix it but will hopefully help me diagnose once
it occurs again.
|
|
|
|
the 64-bit output/input. On i386, this means that the 64-bit value is in
eax:edx, but on amd64 gcc this is not the case (might be a gcc bug, or might
be intentionally different and annoying?). The consequence is that amd64
errata were not always being matched (and then "corrected" using the magic
repair code). We need to compose/decompose the 64-bit value like the
un-locked msr functions do.
originally pointed out by ragge, ok kettenis jsg
|
|
|
|
|
|
ok henning@
|
|
the boot loader passes a variable that identifies the disk its
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
ok krw@ weingart@
ithe boot loader passes a variable that identifies the disk its
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
requested by deraadt@
ok krw@ weingart@
|
|
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
ok krw@ weingart@
|
|
ok deraadt@
|
|
|
|
vaddr_t PMAP_PREFER(..., vaddr_t). This allows better compiler optimization
when the function is inlined, and avoids accessing memory on architectures
when we can pass function arguments in registers.
|
|
tested on a GENERIC config from all arches.
ok deraadt@ miod@
|
|
no binary change
ok deraadt@
|
|
ok deraadt@
|
|
* check the dying flag in timeout and interrupt handlers
fixes crash when disconnecting cardbus usb adapters
|
|
routine
|
|
in previous sweep (avoid NULL deref if the device didn't fully attach)
|
|
usbd_deactivete() and usbd_is_dying()
* use usbd_deactivate() in activate()/DEACTIVATE
* convert a few more direct checks of the associated bus' dying flag
with usbd_is_dying()
|
|
|
|
free it's resources
* use usbd_is_dying() instead of directly checking the device's
bus dying flag
|
|
* add usbd_deactivate(), which should be use to set the dying flag in
struct usbd_device
* add usbd_is_dying(), which can be used to check if either the device
or the associated bus dying flag has been set
* use usbd_is_dying() to check if the deivce or bus is dying before
issuing transfers or requests
|
|
configuration space. So on pyro(4) and vpci(4) return the size appropriate
for the extended PCIe configuration space.
ok miod@
|
|
Re-initializing the pool everytime nfsd(8) terminates is very bad since it
screws up the list of pools resulting in infinite loops when traversing that
list. Issue found by Daniel Melameth.
ok deraadt@
|
|
|
|
the PCIOCREAD and PCIOCWRITE ioctls.
ok kettenis@ (also ok mikeb@ on an earlier version of this)
|
|
given pcitag_t configuration address space. Currently, all pci controllers
will return the usual 0x100 bytes of PCI configuration space, but this will
eventually change on PCIe-capable controlers.
ok kettenis@
|
|
from loongson but isn't necessary on octeon.
ok syuu@
|
|
a simple bus_space_barrier implementation.
ok syuu@
|
|
|
|
used in cpu_switch() for handling it. Also, delete an unnecessary
instruction that I added while debugging the pm_cpus handling before
ok kettenis@
|
|
ok deraadt@
|
|
because it is always PCKBC_KBD_SLOT
ok miod@, krw@
|
|
|
|
early MD and late MI files must be split up so that vers.o can sneak
between. Issue spotted by bluhm, repair discussed with miod
|
|
|
|
having it linked last is bad (on at least i386 and amd64) because the lapic
is mapped over the start of the data segment -- savecore(8) then reads the
version string for a fixed buffer space, and reads into the lapic area
causing unintended side-effects (at least on Intel X5570 and X5680)
found by pedro, discussed with kettenis and mpf and miod
|
|
ok deraadt kettenis miod
|
|
can't use them anyway.
tested with working umodem by sthen@
ok sthen@
|
|
From PCI Express(R) Base Specification Rev 2.0.
|
|
|
|
This is a single-stream single-band AR9300.
|
|
tested by dlg@, ok jsing@
|
|
ok jsing@
|
|
|
|
|
