| Age | Commit message (Collapse) | Author | Files | Lines |
|
after discussions with beck deraadt kettenis.
|
|
instead of connected to ehci.
ok mpi@
|
|
Read commands were issued via asynchronous transfers and replies were
expected after a fixed tsleep() timeout. Upon timeout zyd simply freed
the xfer even if it was still in-flight within the USB stack. This could
cause havoc such as making all USB ports on the system unusable until reboot.
ehci_freex: xfer=0xfffffe811e63e9d8 not busy, 0x4f4e5155
("busy" here would indicate the xfer is done and marked for being freed)
To fix this, issue read commands with synchronous transfers so the xfer
can always complete. Split read/write code paths into separate methods.
Add a flag that tells us if a reply was received in interrupt context
while the read path waited in tsleep().
With and ok mpi@
|
|
on linux versions before 3.11 i915_pci_probe() doesn't match valleyview
unless i915_preliminary_hw_support is specified as a module parameter.
our drm code is currently based on linux 3.8, so it seems unlikely
that the valleyview support we have works.
|
|
It was never enabled and is apparently unfinished.
ok deraadt@ krw@ claudio@ kettenis@
|
|
|
|
|
|
|
|
no side effect
|
|
it when we hibernate.
ok mlarkin@, miod@, deraadt@
|
|
real impact since this descriptor is not used in the kernel. From NetBSD.
|
|
set the 'dying' flag of a device. Such handlers are useless now that
usbd_detach() already set this flag.
Even if the purpose of this flag is questionnable on OpenBSD because
DVACT_DEACTIVATE acts as a pre-detach event, this is just a first small
step towards the simplification of the autoconf(9) device states.
This cleaning is now possible thanks to the work of pirofti@ to convert
all the USB drivers to properly use usbd_is_dying().
Discussed many times with deraadt@
|
|
workq to taskq
ok jsing@
|
|
that usbd_detach() should only be called by the thread doing USB
bus exploration to prevent attach/detach races.
|
|
by guenther@.
While here set the dying flag of the disconnected device so that most of
the DVACT_ACTIVATE handlers can go.
|
|
This is needed on some (specifically HP) machines to avoid _TMP reporting
a bogus temperature value (temperatures > 4,000 degC), which causes acpitz
to automatically shut down the machine because it thinks it's floating in
lava.
Also ensure that we can accept a temperature reading of 0 degC - we were
previously interpreting 0 degC as "bad temperature data" and not attaching
the thermal zone device. Some machines have ephemeral temperature sensors
that come and go (eg in docks) and we want to make sure we attach those
even if they report back 0 degC on initialization. Fixes some machines
with "failed to read _TMP" errors.
ok deraadt, tested and verified by a few folks on tech@ who were seeing
the thermal zone shutdown isue.
|
|
bluetooth support doesn't work and isn't going anywhere. the current
design is a dead end, and should not be the basis for any future support.
general consensus says to whack it so as to not mislead the unwary.
|
|
We return earlier if the interrupt is masked.
Discussed with and okay mpi@
|
|
and specifyig the wrong DWORD count. Moreover we should not evaluate _PDC
if _OSC is present. Might not be perfect yet, but what we had previously
was uterrly and totally wrong.
ok guenther@
|
|
should be, in bytes.
currently uses SENSOR_INTEGER as sensor type, this may change in the future in
favor of a new sensor type.
ok sf@
|
|
|
|
whitespaces while here.
|
|
Remember initprocess instead of initproc.
ok matthew@ blambert@
|
|
size (kern.bufcachepercent) on resume, for better hibernate performance.
ok beck@
|
|
explore thread will not disconnect the root hub. The flag will be
set before detaching the children, like it is done during a suspend-
resume cycle.
Fix a panic when unplugging a cardbus *hci(4).
|
|
|
|
ok mlarkin@
|
|
the disciplines right after vfs_shutdown().
This change is required in order to be able to set `cold' to 1 before
traversing the device (mainbus) tree for DVACT_POWERDOWN when halting
a machine. Yes, this is ugly because sr_shutdown() needs to sleep. But
at least it is obvious and hopefully somebody will be ofended and fix
it.
In order to properly flush the cache of the disks under softraid0,
sr_shutdown() now propagates DVACT_POWERDOWN for this particular subtree
of devices which are not under mainbus. As a side effect sd(4) shutdown
hook should no longer be necessary.
Tested by stsp@ and Jean-Philippe Ouellet.
ok deraadt@, stsp@, jsing@
|
|
does not match the hardware address.
This change only matters for xHCI buses where the controller assigns
device addresses. But it is the simplest way to comply with the stack
requirement of assigning the first `logical' address to the root hub
device.
Device addresses are not much used anyway and a cleanup will follow to
avoid possible confusions.
This makes usbdevs(8) correctly report devices connected to xhci(4).
|
|
|
|
fixes a panic, reported by paul de weerd.
|
|
descriptor.
Pointed out by benno@
|
|
|
|
|
|
|
|
- whitespace cleanup
ok sf@
|
|
|
|
ok by miod@ and deraadt@
|
|
even knows your children! So let him handle the seperation correctly.
Do not rewrite your own custom config_detach_children(9) and as a bonus
start removing the usbd_port tentacles from the stack.
ok pirofti@, yuo@, miod@, deraadt@
|
|
hardware the revision is zero. Linux also hardcodes this value.
ok reyk
|
|
address, kill some no longer true comments and create a proper
function to assign an address.
For the moment, an address is assigned when setting up a slot for a
new device.
|
|
explicitly set it when required.
Right now xhci(4) does not need such function because it assigns
addresses when the first pipe of a device is opened.
ok yuo@, pirofti@
|
|
ok miod@, deraadt@, tedu@
|
|
|
|
when filling the rx ring. trust the hwm.
problem found by sthen@
|
|
|
|
don't need to be married.
ok guenther miod beck jsing kettenis
|
|
|
|
ok mpi
|
|
to using if_rxr.
cut the reporting systat did over to the rxr ioctl.
tested as much as i can on alpha, amd64, and sparc64.
mpi@ has run it on macppc.
ok mpi@
|