On Thu, Dec 17, 2020 at 8:11 PM Mayuresh <[email protected]> wrote: > > On Thu, Dec 17, 2020 at 07:42:06AM -0500, m. allan noah wrote: > > I took a quick look at the protocol and did not recognize it. > > > Perhaps someone else will recognize the protocol. > > If that is not recognized, what is the way out? Just play back as it is by > hard coding the values? >
If the windows driver gives you some options, then you make a series of logs each with a different combination of settings. Then compare the logs to determine what changes. Anything that remains, you may have to hard code. > If I were to do that what tools are suitable? I tried python libusb once, > but could not mimic even 1 step, was getting input/output error or timeout > error. If you want to use sane, you copy a backend that seems readable to you, and pound it into shape. For instance, the cardscan backend is small, and uses USB. > Also, the 'END POINT' numbers reported by wireshark (by double clicking on > any event) aren't matching those reported by lsusb or usbmon. So when > mimicing it's unclear which end point numbers to trust. Oddly, the in vs out end points will have a difference in the highest bit (eg, 0x01 vs 0x81), and some logging programs don't show that distinction. I am not sure if that is what you are seeing. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand"
