| 1 |
Frank Peters posted on Fri, 08 Nov 2013 22:25:53 -0500 as excerpted: |
| 2 |
|
| 3 |
> The utility usb-devices, which uses libusb, can produce data on the |
| 4 |
> scanner, but lsusb, which also uses libusb but depends on usbfs, fails. |
| 5 |
> |
| 6 |
> Does anyone know to resolve such a problem? How can I get my scanner to |
| 7 |
> be utilized by libusb and sane? |
| 8 |
|
| 9 |
I haven't had a scanner in awhile, but based on what I've read verified |
| 10 |
by what I see for other usb devices, udev creates usb devices in |
| 11 |
/dev/bus/usb. Each usb port is a (three-digit sequentially numbered) |
| 12 |
directory, with the individual device functions on that port appearing as |
| 13 |
(again three-digit sequentially numbered) device nodes. Usually there'll |
| 14 |
only be one such function per dir, but some devices, such as my Logitech |
| 15 |
USB mouse/keyboard, have two or more. |
| 16 |
|
| 17 |
There's also /sys/bus/usb/, which like most /sys/ dirs, contains trees |
| 18 |
with information, in this case about usb devices. I believe that's all |
| 19 |
kernel level, however, with udev in fact using some of the information |
| 20 |
found there to populate its udev device tree. |
| 21 |
|
| 22 |
Libusb, meanwhile, has been updated to work with the /dev/bus/usb/ tree, |
| 23 |
so AFAIK that's what you need to create... somehow. |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman |
Archives