Age | Commit message (Collapse) | Author |
|
Based on a proposal of tobhe@.
ok tobhe@
|
|
found by mlarkin
|
|
from Daeil Lee
|
|
|
|
from Daeil Lee
|
|
|
|
|
|
|
|
sufficient to get sdgetdisklabel() to correctly set d_type to
DTYPE_FLOPPY in the default disklabel.
installboot(8) in particular likes to know it is dealing with a
floppy.
ok miod@
|
|
The RTL8153D chipset shares many similarities with the already supported
RTL8156B chip but additionally requires a few semi-unique configurations.
Tested by weerd@
ok jmatthew@
|
|
|
|
Tested with Comfast CF-WU710N v4.
"go ahead" deraadt@
OK stsp@
|
|
For now switch it to cdce(4) until native support is provided by axen(4).
ok bentley@ stsp@
|
|
|
|
|
|
it might be NULL in uhid_intr.
fixes "b_to_q: tty has no clist" panic hit by namn@
tested by thfr@ and namn@
ok anton@
|
|
Reported by Paul de Weerd on bugs@
|
|
Netlock protects `if_list', `ifa_list' and returned `ifa' dereference,
so put netlock assertion within.
Please note, rtable_setsource() doesn't destroy data pointed by
`ar_source'. This is the `ifa_addr' data belongs to `ifa' and exclusive
netlock is required to destroy it. So the kernel lock is not required
within rt_setsource(). Take netlock by rt_setsource() caller to make
`ifa' dereference safe.
Suggestions and ok by bluhm@
|
|
feedback and ok jmc@ miod, ok millert@
|
|
ok mglocker@
|
|
the list comes from the Quectel LTE&5G Linux USB Driver User Guide V2.0
and claims that all these devices function the same as each other.
ok miod@
|
|
|
|
this list comes from the Quectel LTE&5G Linux USB Driver User Guide v2.0
ok miod@
|
|
ok landry@
|
|
|
|
|
|
the Quectel LTE&5G Linux USB Driver User Guide V2.0 says umsm should
only attach to usb interfaces 0 to 3 using the interface class
UICLASS_VENDOR. their doco uses magic numbers, but this is what
they mean.
interfaces 4 and above provide network (not serial) via qmi, ecm,
or mbim. preventing umsm from attaching to the high interfaces
allows the appropriate network driver to use it instead. eg, umb
is now able to attach to the network interface because it presents
a standard mbim class.
discussed with and tested by kevlo@
ok patric@ sthen@ kevlo@
|
|
if umsm_lookup doesnt return anything, return early and leave the
rest of umsm_match to handling specific devices.
no functional change.
|
|
quectel seem to provide a sane and consistent set of functionality
built on top of the qualcomm qmi stuff. their linux drivers guide
says quectel modems provide a set of umsm usb interfaces and a
network interface that can be in qmi, ecm, or mbim mode.
if the modem is in mbim mode, it will present the mbim classes which
umb should be able to attach to without this explicit vendor+product
match (assuming umsm doesn't claim the interface first).
based on info in the Quectel LTE&5G Linux USB Driver User Guide V2.0
discussed with and tested by kevlo@
ok patrick@ sthen@ kevlo@
|
|
ok miod@ millert@
|
|
|
|
here when I split up urtwn_tx() to add support for RTL8192EU devices.
from Mikhail (mp395990 at gmail)
ok stsp@
|
|
No functional change.
|
|
|
|
hardware. Leverage the fact that the same id can be anything within [1, 15] by
using a different id per request in a round robin fashion. Makes it easier to
correlate requests and responses while making sense of the debug output.
|
|
|
|
interrupt keeps firing even if the hos controller has been declared dead.
ok mpi@
|
|
FT232R is either 0 or 0.125.
ok dlg@
|
|
This prevents the kernel from crashing when a ugen(4) device is detached
while kqueue still holds a reference to that device.
Crash reported and fix tested by xavier.s on bugs@.
OK mpi@
|
|
controller on these machines does not see connection events. Instead we
need to rely on the USB PD controllers to notify us of a new connection
and reset the USB controller. This diff implements this by adding a new
tipd(4) driver and infrastructure to notify xhci(4) of new connections.
ok patrick@
|
|
HID++ hardware which should cause battery sensors to be exposed for more
devices. Positive test reports from the following:
* Lift mouse (anton@)
* MX Anywhere 3 mouse (Paul de Weerd)
* MX Ergo trackball (kn@)
|
|
device name and type.
|
|
|
|
In preparation for supporting the unified battery feature.
|
|
uhidpp_device_features().
|
|
the Bolt receiver uses another bit for this which I haven't been able to
identify.
|
|
|
|
hidpp20_battery_get_level_status().
|
|
uhipp_device_features().
|
|
|