[Bug 247727] umass(4) fails when the DropCam device is connected

2020-07-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247727 Bug ID: 247727 Summary: umass(4) fails when the DropCam device is connected Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any Status: New

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Hans Petter Selasky
On 2020-07-02 12:37, Jan Behrens wrote: On Thu, 2 Jul 2020 12:18:02 +0200 Hans Petter Selasky wrote: Hi Jan, I experienced that /dev/usb/2.2.0 and /dev/usb/2.2.1, 2.2.2, 2.2.3, etc. get treated differently when I reset the LimeSDR Mini with "usbconfig -u 2 -a 2 reset". The devices 2.2.1

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Jan Behrens
On Thu, 2 Jul 2020 12:18:02 +0200 Hans Petter Selasky wrote: > Hi Jan, > > On 2020-07-02 12:06, Jan Behrens wrote: > > On Thu, 2 Jul 2020 11:23:32 +0200 > > Hans Petter Selasky wrote: > > > >> On 2020-07-02 11:15, Jan Behrens wrote: > >>> On Thu, 2 Jul 2020 10:54:27 +0200 > >>> Hans Petter

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Hans Petter Selasky
Hi Jan, On 2020-07-02 12:06, Jan Behrens wrote: On Thu, 2 Jul 2020 11:23:32 +0200 Hans Petter Selasky wrote: On 2020-07-02 11:15, Jan Behrens wrote: On Thu, 2 Jul 2020 10:54:27 +0200 Hans Petter Selasky wrote: On 2020-07-02 10:47, Jan Behrens wrote: But wouldn't both drivers require

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Jan Behrens
On Thu, 2 Jul 2020 11:23:32 +0200 Hans Petter Selasky wrote: > On 2020-07-02 11:15, Jan Behrens wrote: > > On Thu, 2 Jul 2020 10:54:27 +0200 > > Hans Petter Selasky wrote: > > > >> On 2020-07-02 10:47, Jan Behrens wrote: > >>> But wouldn't both drivers require access to the entries in /dev ? >

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Hans Petter Selasky
On 2020-07-02 11:15, Jan Behrens wrote: On Thu, 2 Jul 2020 10:54:27 +0200 Hans Petter Selasky wrote: On 2020-07-02 10:47, Jan Behrens wrote: But wouldn't both drivers require access to the entries in /dev ? Yes, user-space drivers would require access to /dev, yes, but kernel drivers not,

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Jan Behrens
On Thu, 2 Jul 2020 10:54:27 +0200 Hans Petter Selasky wrote: > On 2020-07-02 10:47, Jan Behrens wrote: > > But wouldn't both drivers require access to the entries in /dev ? > > Yes, user-space drivers would require access to /dev, yes, but kernel > drivers not, like mouse, keyboard, storage,

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Hans Petter Selasky
On 2020-07-02 10:47, Jan Behrens wrote: But wouldn't both drivers require access to the entries in /dev ? Yes, user-space drivers would require access to /dev, yes, but kernel drivers not, like mouse, keyboard, storage, network. Thus not every user could mess with any USB device, or do I

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Jan Behrens
On Thu, 2 Jul 2020 10:41:42 +0200 Hans Petter Selasky wrote: > On 2020-07-02 10:35, Jan Behrens wrote: > > Thus Linux definitely behaves differently here. My question is: Can > > and/or should FreeBSD be fixed to allow libusb_reset_device() as a user > > or should a driver library be fixed to

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Hans Petter Selasky
On 2020-07-02 10:35, Jan Behrens wrote: Thus Linux definitely behaves differently here. My question is: Can and/or should FreeBSD be fixed to allow libusb_reset_device() as a user or should a driver library be fixed to not use that call. This is an architectural problem. USB devices may have

Re: USB reset fails when using a LimeSDR Mini on FreeBSD

2020-07-02 Thread Jan Behrens
On Sat, 27 Jun 2020 18:04:20 +0200 Gary Jennejohn wrote: > On Sat, 27 Jun 2020 17:53:01 +0200 > Tomasz CEDRO wrote: > > > [...] > > Lookig at the libusb code, libusb_reset_device() only returns an error if > resetting the device fails. Unfortunately it returns -99 (LIBUSB_ERROR_OTHER), which