Okay, over to USB

D54218: Introduce libusb20_dev_open_with_flags for shared vs. exclusive access.
rebased

D54296: PR 291774: expand range of errors reported by libusb_open(3)
rebased to latest

D54231: libusb20_dev_open(3) and libusb20_be_device_foreach(3) man pages.
Fixed linter warnings.

Hey Rick! Thanks for the ping. Tip: use the linter,

mandoc -Tlint here/is/the/manual

D54218: Introduce libusb20_dev_open_with_flags for shared vs. exclusive access.
RETURN VALUES

D54218: Introduce libusb20_dev_open_with_flags for shared vs. exclusive access.
punctuation

D54231: libusb20_dev_open(3) and libusb20_be_device_foreach(3) man pages.
punctuation

D54231: libusb20_dev_open(3) and libusb20_be_device_foreach(3) man pages.
RETURN VALUES and fix unwanted line break in Bl/El list.

Superseded by D52861 and D52862

rebase

More typo fixes and drop __FBSDID tags

Roll typo fixes into this revision

thanks for your review!

Remove nhi_compat.h, typo

I give this a quick look over and left a couple of comments/questions. That said, I think it's reasonable to commit this to the tree and iterate on it there.

Accept all USB4 class PCI devices in nhi_pci_probe

Fixes

Fixes

Stuck on athn_usb_detach code or executes athn_usb_stop multiple times
I suspect this is due to the msleep on one threat and a wakeup on another, but I am not certain how to isolate the problem.

Current Problem: Running into a recursive mutex based on FreeBSD/OpenBSD mutex styles.

Working to update the athn_usb_init, currently working through the newstate handler.

Add missing router defines.

Don't touch router defines; this should be done in D49452.

In D49884#1137462, @imp wrote:

In D49884#1137457, @lwhsu wrote:

I think the current idea is avoiding directly import firmware file into repo. Perhaps we can separate the firmware out. The current approach is using firmware ports/pkg, before having that, we can just put it somewhere and ask people to grab it and put to the required place, for testing.

Or point them at the linux wireless firmware archive repo....

In D49884#1137457, @lwhsu wrote:

I think the current idea is avoiding directly import firmware file into repo. Perhaps we can separate the firmware out. The current approach is using firmware ports/pkg, before having that, we can just put it somewhere and ask people to grab it and put to the required place, for testing.

I think the current idea is avoiding directly import firmware file into repo. Perhaps we can separate the firmware out. The current approach is using firmware ports/pkg, before having that, we can just put it somewhere and ask people to grab it and put to the required place, for testing.