Alan Stern wrote: > No, I said to look at the "up" _reports_. "report" != "packet". > > For IN transfers (from the device to the host), yes, the transfer data > is displayed in the "up" report. For OUT transfers (host to device) > the transfer data is displayed in the "down" report. For control > transfers, both reports contain a section labelled "Setup packet" but > the values in the "down" report are wrong. > > OK, here is what I have done. After opening the dev, setting the configuration and claiming the interface, I am sending a control message of bRequestType = 0x42, bRequest of 0x06, all other values = 0. This is the first "out up" packet sent to the device according to SnoopyPro. The transfer from this times out so I'm obviously missing something. Of course, the report immediately before this one is an "out down" but you suggested that these aren't of concern. FWIW: this is a "Vendor Endpoint" function (0019) and has the illogical bRequestType of 0x00. I know - can't trust the down reports in Snoopy - I'm going to look for a different USB analyser. I'm wondering if there is more to this transfer than meets the eye though since it's already "off the books" as far as the standard goes.
The first question that seems germane: is the value of "PipeHandle" important? Is there a clean way to set it (I'm using libusb for now). Ron Gage ------------------------------------------------------------------------- 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-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
