Hi, On Sun, Dec 12, 2004 at 05:02:33AM +1100, Braken wrote: > So I suppose what I'm really asking is some information on where to > start. What should I be looking for in the snooping logs, how to I > decipher them?
That really depends on the scanner. If we would know how the protocol works, there already would exist a driver :-) > How does scanner communication usually work, what kind of > commands are common in communication with scanners and what do the > commands actually do? Are these even the questions I should be asking? I > don't expect people to answer these questions here, but links to pages > with this kind of information would be helpful, as I can't seem to find > anything in my searching (I'm probably just not searching for the right > thing). Maybe this can help you a bit: www.eol.ca/~mmather/scanner.html > I've saved a log of a single small scan, and it was 7800 lines long. Is > this normal? No, that's rather short :-) Check for repeated commucation. This can be checking of scanner buttons or waiting for the scanner to get ready. > I found out the endpoints from the logs -- > > 0x00 control > 0x81 bulk/interrupt transfer in > 0x02 buld/interrupt transfer out > > -- but that really is all I've been able to work out, other than that > there seems to be a constant stream of control commands when there's no > scanning taking place, which I'm assuming is the driver checking for > button presses. What's the format of the control commands? Are bulk endpoints used at all? Bye, Henning
