Age | Commit message (Collapse) | Author |
|
the device has multiple interfaces and/or report IDs.
Make sure utpms(4) only matches the mouse interface of the HID device
embedded in Powerbooks and do not rely on the alphabetical order to
have a working ukbd(4) on such machines.
Problem reported by daniel@
|
|
|
|
DVACT_QUIESCE was not passed to usb(4) and a new uhub(4) device was
reattached at every resume.
Problem reported by mlarkin@
|
|
|
|
Committing over MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R).
Tested by myself, matthieu@, juanfra@
Diff glanced over by kettenis@
|
|
|
|
|
|
giving you the original capacity of the battery:
hw.sensors.acpibat0.watthour0=64.07 Wh (last full capacity)
hw.sensors.acpibat0.watthour4=84.24 Wh (design capacity)
hw.sensors.acpibat0.amphour0=2.03 Ah (last full capacity)
hw.sensors.acpibat0.amphour4=4.40 Ah (design capacity)
Diff from Fabian Raetz on tech@, thanks!
ok mlarkin@ zhuk@ armani@ kettenis@
|
|
it in one place.
|
|
there to our port lists, then find the next available loop id and carry on
rather than restarting. This way, we're less likely to get stuck looping
when the firmware behaves inconsistently. We also don't need to treat domain
controller logins specially.
|
|
|
|
|
|
the ring is halted.
Do not bother reporting USBD_STALLED to the stack like other HC drivers
do since the endpoint is automatically reseted. What is the point of
this error apart from making sure driver authors will forget to call
usbd_clear_endpoint_stall_async() correctly?
The Renesas uPD720202 xHCI, provided by Stefan Wollny, now works as
expected.
|
|
(used only when ACPI_DEBUG is enabled)
From a diff on tech@ by Fabian Raetz, with a minor change by me, tested
on i386 and amd64 with ACPI_DEBUG enabled and disabled.
|
|
|
|
|
|
|
|
|
|
allows ramdisk kernels to build again
|
|
of Mediatek to keep using the free firmware licence we've been using.
Tested by myself, rapha@, Fred Crowson, Dinar Talypov, gerhard@, matthieu@.
|
|
|
|
MADT processing if it is missing. This, combined with an earlier diff
from kettenis@ to fix MADT interrupt polarity processing, should resolve
the issues reported with QEMU/KVM ACPI power button presses when using
OpenBSD guests.
ok kettenis@, pirofti@
tested by myself and kettenis for the past few weeks
|
|
status changes because it might be freed when detaching the root uhub(4).
Also do not reschedule a timeout if the pipe is being aborted.
Finally do not add more code to retrieve the 'bInterval' value of the
root hub endpoint descriptor since this value is hardcoded in the uhci(4)
driver.
|
|
code was masking out bits which were also tested in the same expression.
Reported by cppcheck via jsg@ (Expression '(X & 0xfc) != 0x2' is always true).
Tested with Elantech Touchpad, version 3, firmware 0x250f00.
|
|
|
|
|
|
|
|
Since no DPRINTF() call remains also remove its definition (requested by mpi@).
ok mpi, and also reported by Jean-Philippe Ouellet
|
|
|
|
|
|
|
|
|
|
|
|
there to our port lists, then find the next available loop id and carry on
rather than restarting. This way, we're less likely to get stuck looping
when the firmware behaves inconsistently. We also don't need to treat domain
controller logins specially.
additional complications discovered by deraadt@
|
|
usbd_xfer pointer to the routines processing finished transfers to make
it crystal clear that the timeout and abort logic is the same everywhere.
|
|
host controller because autoconf(9) already does it.
|
|
Previous uchcom(4) driver targeted old one, and new one could not work
because of uchcom_set_line_control() broke the value of
UCHCOM_REG_LCR1(0x18).
To support new CH340, uchcom_set_line_control() and uchcom_reset_chip()
have been overhauled. Current uchcom(4) does not change the value of
UCHCOM_REG_LCR1 register, it means even/odd parity mode is no longer
supported with old CH340.
ok by mpi@
|
|
|
|
Diff from Lukasz Ratajski
ok sthen@
|
|
|
|
|
|
since it is only freed when your keyboard is detached.
|
|
don't need check cmd twice.
ok miod@
|
|
it possible to use the non-mappable part of the GTT, prepares the way for
using the PPGTT and reduces the diffs with Linux.
ok jsg@
|
|
input device descriptors, notably if they include an Item with an
Usage array (Min-Max range) and others single Usage elements.
Tested by many, thanks! ok andre@
|
|
delicate. HC drivers do not always accept to be left alone.
I don't know if it is a love crisis, but apparently receiving a root
hub status change interrupt before having an uhub(4) attached breaks
resume.
So make sure the root hub is re-attached before interrupt get enabled.
It is safe to do it during DVACT_RESUME since attaching root hubs do
not require any USB transfer.
Based on a diff from yasuoka@, fix a regression introduced in last
commit an reported by Abel Abraham Camarillo Ojeda on tech@ and Nils
R on bugs@.
|
|
ok deraadt@
|
|
|
|
This leak is similar to the public xfer leak #1 that was affecting
device interrupt pipes except that root hubs are rarely detached.
Note that this xfer is never associated to any TD and is just used
to indicate that some of the HC ports has changed status, so there
is no need to flag it as "done" before completing it.
|
|
|