On Mon, Mar 20, 2000 at 10:58:04PM +0000, Torsten Howard wrote:
Before you invest any more time, there is a chance that the problems
you are seeing are caused by the USB system. The several minutes time
outs are also seen with e.g. a Kodak camera. That's also the reason
why I'm not doing anything in the backend code at this time. I just
got confirmation that the latest backend code is still working with
a Perfection 610.
> Anyways, here are a few questions for the knowledgeable:
>
> Does scanimage determine the scanner identity from these 'S:' entries, as seen in the usb/devices file?
No. The EPSON backend get's the scanner manufacturer and name from
a command that's send to the scanner.
> What could the access to the scanner driver change, such that the usb susbsystem can no longer identify the scanner?
USB errors?
> How, exactly, are scanner identities determined? Inside each individual driver code? By standard mechanism? Are there differences between the USB/SCSI command requests (esp. for the epson)?
Yes, each backend does this. In the case of the EPSON backend the SCSI and USB
scanners are treated the same way. The command set is the same.
> Oh well, it's ten pm and I must study for dynamics test. More on this later.
Good luck,
Karl Heinz
-- Karl Heinz Kremer khk@khk.net http://www.khk.net
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Mon Mar 20 2000 - 19:11:41 PST