> One way to address this has been prototyped for printers:  let the
> hotplug subsystem tell the scanner subsystem about device types,
> since it's already got that data available:

This does not help you on installation, which causes most problems.

[..]
> Or, it could go the other way around.  If you're scanning /dev/...
> nodes, add a corresponding ioctl to find which USB device is
> involved, and then use the existing USB support to find VID/PID.

This is very helpful.
We should do this as generic as possible.

> And there's also Alan's suggestion, to do scanner drivers entirely in
> usermode, focussing development work on usbdevfs and APIs to it.
> (I think the Java USB API is more powerful than libusb, but that can
> just be a hacker challenge ... :)

1. No persistent device permissions
2. Some scanners have interrupt endpoints
3. Very hard to use without hotplugging, which is beta at best
4. There was this little problem with control messages and usbdevfs

In this case I disagree with Alan.

        Regards
                Oliver

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to