Age | Commit message (Collapse) | Author |
|
|
|
|
|
attached audio device, i.e. audio0. This approach does not work well
while using additional audio devices equipped with physical volume keys
since those would only affect the volume of audio0.
Instead, correlate audio and ucc devices attached over USB in order to
adjust the volume of the correct audio device. This is done by passing a
cookie from the common point of attachment which is later used to
correlate the audio and wskbd device.
The same approach could be adopted for audio and wskbd devices attaching
on a different bus. Keep in mind that it's of importance to make use of
and increment the same global cookie identifier to avoid collisions.
Makes the volume keys on my Logitech G435 Headset do the right thing.
ok ratchov@
|
|
unused but intended to be used to correlate audio and wskbd devices.
ok ratchov@
|
|
same receiver. Prevents a newly added assertion from triggering.
Problem reported by Joel Carnat <joel at carnat dot net> on bugs@
|
|
apostrophe.
|
|
USB transaction is finished when whole requested data has transferred,
or short packet (the size is less than wMaxPacketSize) has sent.
UCHCOMIBUFSIZE(256) was multiply of wMaxPacketSize(32). When CH340 sends
exact wMaxPacketSize byte packet, this will cause Rx jam problem
due to transaction is not finished.
Now uca.ibufsize is same as wMaxPacketSize to avoid this problem.
ok kevlo@
|
|
|
|
switch has a default case and umb_ncm_setup_format() ensures that
only 16 and 32bit formats are accepted. Fixes build error without
DIAGNOSTIC set.
Found by and OK robert@
|
|
feedback and ok tb@ jmc@ ok ratchov@
|
|
ok ratchov@
|
|
from Brad
|
|
Works for me on amd64.
ok hastings@
|
|
ASUS USB-N10 v2, D-Link DWA-127 rev B1, Edimax EW-7711UAn v2,
various Ralink/MediaTek ids.
ok stsp@
|
|
|
|
ASUS USB-N10 v2, D-Link DWA-127 rev B1, Edimax EW-7711UAn v2,
various Ralink/MediaTek ids.
ok stsp@
|
|
|
|
|
|
ok anton@
|
|
Not enabled yet. Pending firmware availability.
ok stsp@ jmatthew@
|
|
Ported from run(4) with legacy chipsets removed.
Not yet enabled in the build.
ok stsp@ jmatthew@
|
|
A multi-port CP210x device presents each COM port as a separate USB
virtual COM port interface. When attaching uslcom(4), take the USB
interface from the attach arguments instead of using interface 0.
This lets the driver access the different ports of a quad-port CP2108.
Tested with a single-port CP2102 by jsg@
OK jsg@ deraadt@
|
|
ok anton@
|
|
ok bluhm@
|
|
conditional. Repeating the previous commit messsage:
Assert that at least one report id is claimed during multiple report ids
attachment. Should prevent uhidev drivers from doing the wrong thing in their
corresponding match routine.
Tested by dv@
|
|
|
|
return EINVAL after the first frame size has been returned in the
VIDIOC_ENUM_FRAMESIZES ioctl.
ok mpi@
|
|
USB HC drivers; M_DEVBUF -> M_USBHC.
ok kettenis@
|
|
|
|
attachment. Should prevent uhidev drivers from doing the wrong thing in their
corresponding match routine.
|
|
|
|
|
|
tested and ok ian@
|
|
|
|
|
|
uhidev drivers have been fixed.
|
|
|
|
* USB device drivers use M_USBDEV instead of M_DEVBUF.
* USB HC drivers use M_USBHC instead of M_DEVBUF.
In a vanilla setup, this enlarges the USB memory pool.
ok anton@
|
|
|
|
a lot more knf could be sprinkled in this file...
|
|
they get confused if you try to configure them and don't work at
all otherwise. CH341 seems fine otherwise.
from miod
tested by me and Felix Kronlage-Dam
|
|
|
|
|
|
uhidev_open() and uhidev_close(). In uhidev_close() the UHIDEV_OPEN flag
is cleared early on but the same thread can end up sleeping while
closing the input or output pipe. This allows another thread to enter
uhidev_open() but only to fail opening either the input or output pipe
since they are already open for exclusive use. The uhidev_open() error
path frees the input buffer but leaves a dangling pointer around;
causing uhidev_close() to free the same buffer.
This can at least happen on xhci(4) which can end up sleeping in
xhci_pipe_close().
Reported by and ok gnezdo@
|
|
report id to signal that multiple ones should be claimed by the match
routines does not work. All valid report ids 1-255 cannot of course be
used and 0 which is reserved by the USB HID specification is internally
used to represents devices lacking an explicit report id.
Therefore, use presence of the claimed array to signal that multiple
report ids can be claimed.
Tested by gnezdo@
|
|
report ids conflict, extract the claim multiple report ids conditional
in order to minimize the required upcoming changes to resolve the
conflict.
Tested by gnezdo@
|
|
UHIDEV_CLAIM_MULTIPLE_REPORTID conflict.
Breaks fido(4) as reported by gnezdo@
|
|
time without using sentinel that cannot be represented using a single
byte. Instead, use 0 as this report ID is reserved according to the USB
HID specification. Fixes attachment of some upd devices which exposes up
to 256 report IDs.
Thanks to Damien Couderc <openbsd at petrocore dot eu> for reporting and
testing.
|
|
the reportid locator. The same locator was removed in 2004 making the routine
redundant.
ok gnezdo@ mpi@
|
|
Thanks to Damien Couderc <openbsd at petrocore dot eu> for testing and ok
gnezdo@
|