Date: Wed, 9 Jan 2008 14:08:55 -0500 From: Mikhail Teterin <mi+mill@aldan.algebra.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: johnjen@reynoldsnet.org, R.Tobin@ed.ac.uk, usb@freebsd.org, Mikhail Teterin <mi+kde@aldan.algebra.com> Subject: Re: BlackBerry (Re: using libusb) Message-ID: <200801091408.57437.mi%2Bmill@aldan.algebra.com> In-Reply-To: <200801091934.54053.hselasky@c2i.net> References: <200801090114.56195@aldan> <200801091015.17730@aldan> <200801091934.54053.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=D3=C5=D2=C5=C4=C1 09 =D3=A6=DE=C5=CE=D8 2008 01:34 =D0=CF, Hans Petter Sel= asky =F7=C9 =CE=C1=D0=C9=D3=C1=CC=C9: > My plan is to extend /dev/usbX so that it becomes a so-called clonable > device. When you open up "/dev/usb0.2.3" for example, you open up the > device having index 2 on USB bus 0 and endpoint 3. This will need some > modifications in libusb. Ugen will still be there, but I plan to move the > functionality over to "usb.c". Accessing endpoints will then work > regardless of what drivers are hooked on. I must admit, that /dev/umass2 looks better than /dev/usb0.2, but I don't=20 really care :-) Other than that you will, probably, have to take over=20 maintainership of the libusb port... Maybe, even to the point of bringing i= ts=20 relevant bits and pieces into the src-tree. There is simply too much stuff being written for Linux that uses the libusb= =20 API to ignore it... It is bad enough, that we can't have video4linux=20 support :( > Some open problems that needs to be resolved: > > Should we allow parallell access to USB interfaces? Not sure, what you mean. Parallel access between multiple interfaces to the= =20 same device (umass and ugen access to the same blackberry), or parallel=20 access between two different user-space processes? > And what about rights management? devfs.conf? -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200801091408.57437.mi%2Bmill>