On Wed, 18 Apr 2007, John Wojnaroski wrote: > Alan Stern wrote: > > >On Wed, 18 Apr 2007, John Wojnaroski wrote: > > > > > > > >>OK, so an IN transfer might look something like <22 09 0200 0000 0000> > >> > >> > > > >Except that it couldn't use 0x22 in the first byte. The high-order bit of > >that byte determines the direction. It would have to be 0xa2. > > > > Then why does the SnoopyPro log indicate that the above byte stream > illicits a response from the device, or am I mis-reading the log?
Please be more specific. Which URBs in the SnoopyPro log are you referring to? Numbers 7, 8, 10, 12, 14, and so on? Unforunately the log doesn't seem to mention the endpoint number or the direction for those transfers, but it does say that they are Bulk or Interrupt. So whichever endpoint they use, your program needs to use. > Given the SnoopyPro log I provided with the device working under > Windows, seems it would be a routine matter to determine what the device > expects and how to build the URB with linux calls. Except, for someone > like myself who is just beginning. Perhaps this is the wrong forum for > this sort of help. No, it's the correct place. But you should start out by learning the basics. Read through parts of the USB 2.0 spec and then you'll be in better shape. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
