On Sun, 2002-12-08 at 19:59, David Colburn wrote: > USBview offers a good deal of hardware detail about the devices but > nothing about where they are for the purpose of mounting and accessing > them.
It is up to the driver to set up a userland interface. And there can be several different interfaces for the same hardware. For example, a scanner can be: - a scanner device, accessible with a SANE backend - a Video for Linux device, accessible with your favorite TV viewer - a HID device, so that OS knows when you press a button on the scanner So there is no single and simple answer to "where they are". > It seems very odd that USBview can see these devices from the user level > in Bash but RedHat 8.0 does not pick up the devices on boot. That is probably because RH does not have a driver. USBView is just reading from the device itself - all these ID strings and numbers are encoded inside the device. Even if you can read that the device #7 is a "XLAIXU Global Disintegrator Key" (which is conveniently sold at http://www.villainsupply.com/doomsday.html ) you only can print this string, since the USB vendor device itself is useless without a special driver written specifically for this device. > I am told that USB is a rather oversold and quirky interface. It's quite obvious, isn't it? :-) > Is there > a simple way to convince RedHat to talk to these devices, please? All class-compliant devices (such as mouse, keyboard) are automatically serviced already. Vendor devices need drivers, and usually only manufacturers of those devices can write these drivers. Some devices that pretend to be class-compliant are broken nevertheless, and require custom workarounds here and there. Such is life. Dmitri
signature.asc
Description: This is a digitally signed message part
