On Sun, 22 Jul 2007, Ron Gage wrote: > OK, I'll be the first to admit that doing USB work is a new area for me > and I might have some terminology conflated. That said, I can only go > by what is in front of my eyes. > > That said, I am using the data as reported by SnoopyPro. > > 4 in down n/a 2.925 VENDOR_ENDPOINT - > URB Header (length: 80) > SequenceNumber: 4 > Function: 0019 (VENDOR_ENDPOINT)
Umm. I'm not familiar with USB programming under Windows, so I can't say what (if anything) the "Function: 0019" means. It's probably something specific to the Windows USB API and not meaningful in other operating systems. > PipeHandle: 00000000 > > SetupPacket: > 0000: 00 81 80 00 00 00 00 00 You have failed to realize something important about SnoopyPro: The Setup packet values displayed in the "down" section for an URB are garbage. Only the values displayed in the "up" section are correct. Don't ask me why; I didn't write SnoopyPro. > bmRequestType: 00 > DIR: Host-To-Device > TYPE: Standard > RECIPIENT: Device > bRequest: 81 > unknown! > > No TransferBuffer > > > This is what I am trying to recreate as this particular packet is sent > multiple times. It's the wrong thing to recreate. Look at what the "up" section says and recreate that instead. You can use usb_control_msg(). Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
