> In http://www.geocrawler.com/mail/msg.php3?msg_id=9767006&list=2571
> it was proposed to just remove this check. However, doesn't this mean
> that the scanner driver attaches to both interfaces, so the printer
> would be mistaken for a scanner?
You have to check for the interface to be of the vendor specific class.
That'll help if the other interface is a printer.
> A different approach involving more work would be to add the interface
> number that represents the scanner part of the device to the list of
> ids in scanner.h. Is the assumption correct that the index of the
> interface (ifnum) stays constant? E.g. if ifnum=1 for the scanner
> device for a multi-function device, will it be 1 everytime I plug in
> the device?
>
> So the entries in scanner.h would look like this:
> { USB_DEVICE(0x04a5, 0x2060), 1 }, /* Prisa Acerscan 620U &
> 640U(!)*/
>
> And there would be a test for the interface number instead of the
> above mention test for the total number of interfaces.
>
> Comments? Other ideas?
This is only needed if a device has several interfaces of the vendor specific class.
Regards
Oliver
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
