I'm happily David Nelson's USB scanner driver with my Epson 610 scanner,
on a Debian 2.1 2.2.16 box w/ the 2.4.0-test2-pre2 backport kindly
provided by SuSE.
I'm using sane (with Karl Heinz's epson patches), which unfortunately
core dumps every so often. When it does, it seems to leave the USB
scanner driver in an uncertain state.
When this happens the device is "locked out" - any further opens fail (I
get the "funky result" or "NAK" errors), or block indefinitely. I guess
the error I get depends on what state the scanner was left in.
The only way I've found to reset the scanner is unloading the scanner
module and reloading it (i.e. modprobe -r scanner && modprobe scanner).
I'm very much a novice when it comes to kernel stuff, though I presume
that when a user-level program dies and closes all its file handles,
scanner.c's close_scanner is called?
>From scanner.c's close_scanner function it seems nothing special is done
to 'flush' or reset the device when it's closed. Is it possible to reset
the scanner when it's midscan?
I guess to do this via a scanner command would not be possible (assuming
that every scanner has it's own way of doing things), but as I noted
above the process of unloading/reloading the module does effectively do
a reset - I guess this is at the USB interface level?
Is it possible to initiate such a reset from the scanner driver?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]