src/lib/libusb/libusb10.c, branch releng/14.2

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

2023-08-16T17:54:29+00:00

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

spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD

2023-05-12T16:44:03+00:00

The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with:		pfg
MFC After:		3 days
Sponsored by:		Netflix

libusb(3): Implement libusb_init_context() and the needed structures and definitions.

2023-03-30T15:26:55+00:00

Differential Revision:	https://reviews.freebsd.org/D38212
MFC after:	1 week
Sponsored by:	NVIDIA Networking

libusb(3): Implement libusb_interrupt_event_handler() by exposing existing function.

2022-10-02T15:32:59+00:00

MFC after:	1 week
Sponsored by:	NVIDIA Networking

libusb(3): Ignore SIGPIPE when initializing the LibUSB v1.0 API.

2022-03-02T11:33:40+00:00

The LibUSB v1.0 emulation layer uses pipes internally to signal between
threads. When USB devices are reset, as part of loading firmware, SIGPIPE
may happen, and that is expected and should be ignored.

PR:		261891
MFC after:	1 week
Sponsored by:	NVIDIA Networking

Improve handling of USB device re-open in the LibUSB v1.x API.

2021-06-11T15:06:44+00:00

Make sure the "device_is_gone" flag is cleared after every successful open,
so that the "device_is_gone" flag doesn't persist forever.

Found by:	sergii.dmytruk@3mdeb.com
PR:		256296
MFC after:	1 week
Sponsored by:	Mellanox Technologies // NVIDIA Networking

libusb: improve compatibility

2020-06-09T17:17:43+00:00

Specifically, add LIBUSB_CLASS_PHYSICAL and the libusb_has_capability API.
Descriptions and functionality for these derived from the
documentation at [0].  The current set of capabilities are all supported by
libusb.

These were detected as missing after updating net/freerdp to 2.1.1, which
attempted to use both.

[0] http://libusb.sourceforge.net/api-1.0/group__libusb__misc.html

Reviewed by:	hselasky
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D25194

libusb: LIBUSB_DEBUG environment variable override of libusb_set_debug

2019-10-02T15:19:39+00:00

The debug level generally just controls verbosity of libusb for debugging
libusb devices/usage. We allow the environment to set the debug level
independent of the application, but the application will always override
this if it explicitly sets the debug level.

Changing the environment is easy, but patching the software to change the
debug level isn't necessarily easy or possible. Further, there's this
write-only debug_fixed variable that would seem to imply that the debug
level should be fixed, but it isn't currently used. Change the logic to use
strtol() so we can detect real 0 vs. conversion failure, then honor
debug_fixed in libusb_set_debug.

Reviewed by:	hselasky
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D21877

Fix typos in libusb.

2019-03-05T14:47:15+00:00

Found by:		Denis Ahrens 
MFC after:		1 week
Sponsored by:		Mellanox Technologies

Fix issues about cancelling USB transfers in LibUSB when the USB device has

2018-09-12T15:06:30+00:00

been detached. When a USB device has been detached the kernel file handle
stops responding to commands. USB applications which continue to run after
the USB device has been detached, depend on LibUSB generated events to tear
down its pending USB transfers. Add code to handle the needed cleanup when
processing the USB transfer(s) fails and prevent new USB transfer(s) from
being submitted.

Found by:		Ludovic Rousseau 
PR:			231076
MFC after:		1 week
Approved by:		re (gjb)
Sponsored by:		Mellanox Technologies