Date: Mon, 24 Oct 2005 22:54:30 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-usb@freebsd.org Subject: Re: LibUSB fails to enumerate all devices Message-ID: <200510242254.31406.hselasky@c2i.net> In-Reply-To: <041301c5d8d4$62749100$6600000a@venti> References: <20051023095137.GC18930@alzatex.com> <041301c5d8d4$62749100$6600000a@venti>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 24 October 2005 21:51, Brian K. White wrote: > ----- Original Message ----- > From: "Loren M. Lang" <lorenl@alzatex.com> > To: <freebsd-usb@freebsd.org> > Sent: Sunday, October 23, 2005 5:51 AM > Subject: LibUSB fails to enumerate all devices > > I am developing a USB device which has two interfaces, one interface > uses a standard HID protocol, the other is completely custom at the > moment. FreeBSD attaches appropriately to the HID interface and works > correctly. For the custom interface, I was going to write a device > driver in userspace using libusb, but I can't seem to find it. I wrote > a program to enumerate all devices on all busses, but the only device I > see is the one device I don't have any driver loaded for. Does FreeBSD > not allow a userspace to access an interface of a usb device when any of > it's interfaces are grabbed by a kernel driver even though the interface > I want is not grabbed? No. ugen, which is the device libusb is searching for, is only created when no subdevices has been attached. It is not impossible to have a shadow "ugen" hanging on all USB devices, but it is a little complicated, because you get two applications that can set the configuration: ugen and the USB device driver. Whenever the configuration number is set, all ugen devices in /dev must be re-created, and one should detach existing, attached USB sub-devices. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510242254.31406.hselasky>