Stephan Feder <[EMAIL PROTECTED]> wrote: > Pieter Nagel wrote: > ... > > However, I believe for 2.5 the loop should be rewritten as retry loop, > > and the function should immediately return whatever it reads, like the > > majority of drivers do. As a side effect, the number of retries on > > TIMEOUT/NAK would change, so the TIMEOUT values for various scanners > > would need to be retuned based on experience. > > The scanner module does blocking IO. You cannot change it to any kind of > nonblocking IO without breaking applications. It would be wise to ask > application developers first, e.g. on the SANE developer mailing list > ([EMAIL PROTECTED]).
FYI, FWIW: This is not merely a Sane issue. This is a _kernel_ issue. The problem in question causes a kernel Oops, a complete hang of the kernel USB scanner module, and is present also with _another_ application program, i.e. Vuescan. Regards, -- Jon ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
