From: DG <dg...@um...> - 2000-09-26 06:12:15
|
>BTW, there is still another problem with the kernel drivers which causes >more-or-less random lockups of the client process, for example, when doing >a large scan. If you're able to do anything about that or even just have >any ideas on what could be causing it, it would be much appreciated too. :-) I've spent a little time reaquainting myself with the code, and I think I can take a shot at this. Fortunately (maybe), it hangs reliably with debugging turned on, suggesting a timing issue (interrupt scheduling conflicts maybe?). I want to start with a small scan like maybe 'scanimage --test', but I don't know how the protocol works. How can I find out what the data exchange should look like between the driver and scanner during a scan? Something like a step-by-step explanation would be best. A dump of the incoming and outgoing data would also help. Then I can compare what I'm getting with what I should be getting and hopefully find out where the error is creeping in. ZZZ-dgun-ZZZ-@-ZZZ-umpire.com-ZZZ (Remove the Z-'s to reply) ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup |