src/lib/libusb, branch release/14.4.0

libusb: add SUPER_PLUS in speed enum.

2025-06-23T07:40:33Z

Summary: Some application(like usbmuxd) start to use LIBUSB_SPEED_SUPER_PLUS now. Though we don't have the corresponding infra in kernel right now, it is harmless to have this enum value in userspace to prevent the compile error Reviewed By: bapt Sponsored By: FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D50359 (cherry picked from commit f938c0a90313125a9518307e80ca92d4c71f7745)

libusb: use eventfd

2025-06-23T07:40:33Z

Simplify libusb code by replacing pipe(2) inter thread event mecanism with eventfd(2). MFC After: 3 weeks Reviewed by: kevans Differential Revision: https://reviews.freebsd.org/D50360 (cherry picked from commit ae28929b7c78267815e994e0ad12e3cc7db361bc)

libusb(3): Fix link in comment

2025-05-14T14:42:13Z

Event: Advanced UNIX Programming Course (Fall’23) at NTHU. Pull Request: https://github.com/freebsd/freebsd-src/pull/1042 (cherry picked from commit 2a3a8eb9fac66183e5af4852bbcb40824629f182)

libusb: Emit event after deregistering hotplug handler

2025-05-14T14:23:38Z

The original implementation did not emit an event when a hotplug handler was deregistered. This omission causes issues for programs that follow the best practices recommended by libusb—particularly those that use `libusb_hotplug_register_callback()` or similar functions in a loop while managing hotplug handlers dynamically. Without emitting an event after deregistration, these programs can become stuck waiting indefinitely for an event that will never come, as the condition to break out of the wait loop is never satisfied. See: https://github.com/libusb/libusb/blob/6c0ae1ab456da49e7805115e77ce0428ace4ea41/libusb/hotplug.c#L459 Reviewed by: bapt Sponsored By: FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D50170 (cherry picked from commit d2852659180307475a8376ce86aa587cccbb10bf)

libusb: fix hotplug sigbus

2025-01-07T09:02:57Z

When a hotplug callback has been registered, and the program using libusb is calling libusb_exit then the thread handler is set to NO_THREAD which result in the variable controlling the loop the be set to 0, it does a last pass through device available without having done a scan, which result in a sigbus after it tried to unregister all the devices. directly break the loop instead and cleanup the list of devices this fixes the tests with LGPLed libusb's hotplugtest program MFC After: 3 days Reviewed by: kevans Differential Revision: https://reviews.freebsd.org/D48298 (cherry picked from commit ba5834b8e11fd002a663d083a464e397e76cb3a9)

manuals: Fix dates

2024-11-04T16:16:22Z

These were reported by `mandoc -T lint ...` as warnings. Signed-off-by: Graham Percival Reviewed by: mhorne MFC after: 3 days Sponsored by: Tarsnap Backup Inc. Pull Request: https://github.com/freebsd/freebsd-src/pull/1475 (cherry picked from commit b74aaa1a2199261f9078247d29481a994b6b5e42)

libusb: claim to be version 1.0.16

2024-08-06T21:25:21Z

We are not 100% compatible with 1.0.16, but implement some functionality from that version that is required by certain ports. PR: 277799 PR: 279555 (exp-run) Event: Kitchener-Waterloo Hackathon 202406 Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45514 (cherry picked from commit 5654b42142e1f689b26d405c90379b85f22349a0)

Remove $FreeBSD$: two-line nroff pattern

2023-08-16T17:55:10Z

Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/

Remove $FreeBSD$: one-line sh pattern

2023-08-16T17:55:03Z

Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

Remove $FreeBSD$: one-line .c comment pattern

2023-08-16T17:54:29Z

Remove /^/[*/]\s*\$FreeBSD\$.*\n/