the device.

This includes a further change to libusb_open_with_vid_pid to skip over fai=
led
attempts to the first successful call to libusb_open.

In an exteme case, this unexpected behavior in the FreeBSD implementation
causes two ports to display the same device 32 times (see ports airspy and
hydrasdr).

As an example, a FreeBSD host has two USB devices attached that share the s=
ame
VID/PID but different serial numbers. The intent is ...

a. a first call to libusb_open_with_vid_pid returns a device handle to the
first matching device - which the app keeps open.
b. a second call to libusb_open_with_vid_pid returns a device handle to the
second matching device (and not the first) - which the app keeps open.
c. a third call to libusb_open_with_vid_pid returns null (and none of the o=
ther
devices).

libusb_close or process exit remove the advisory lock on the device. The
specific advisory lock mechanism is flock(2). A complete patch is included.=
 I
will follow up with a test plan and the bits of code used for testing.

--=20
You are receiving this mail because:
You are the assignee for the bug.=