On 1/3/06, Henning Meier-Geinitz<div><span class="gmail_quote"><b class="gmail_sendername"></b> <<a href="mailto:henning@meier-geinitz.de">henning@meier-geinitz.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Visioneer OneTouch 7600 USB<br><br>Shouldn't it be possible to use the existing viceo backend at least to<br>understand what's send to the scanner? That backend claims to support<br>that scanner.</blockquote><div><br>
It should be possible...but this does not use libusb, it is a patch to the scanner module. There is alot of code there I do not understand.<br><br>I am trying to follow the instructions in backend-writing.txt "write a stand-alone scanning program first". By starting from scratch I am learning alot.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Was it you who entered this bug/wishlist report?<br><a href="https://alioth.debian.org/tracker/index.php?func=detail&aid=302812&group_id=30186&atid=410366">
https://alioth.debian.org/tracker/index.php?func=detail&aid=302812&group_id=30186&atid=410366</a><br><br>In this case, could you provide a description or documentation for<br>this script?</blockquote><div><br>
Yes, <pre>Input to this perl script is the output from a windows usb snoop<br>log.<br><br>This script generates c code using libusb that compiles and executes<br>the same USB commands that were captured in from the snoop.
</pre> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On the other hand, if it has such grave bugs it may be better not to<br>link to it.
</blockquote><div><br>Just like all programs, it will get better as time goes on. It has been the best tool I have found that gives me a jumpstart to understanding libusb. Hopefully in the future this will get included in the libusb project tree.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> I guess OUT OUT should be usb_bulk_write and OUT IN should be usb_bulk_read
<br><br>Yes. These are URBs, not the actual physical data on the USB. That<br>means that the data is just read and not that a buffer filled with<br>zeros is sent to the scanner.<br><br>Also, you can tell if its a read or write by looking at the endpoint
<br>number (if bit 7 is set (0x80), it's an IN endpoint).<br><br></blockquote></div><br>I am going to write a patch and send it in to fix usbsnoop2libusb.pl<br><br><br>-Thanks<br>Steve More<br>