Oliver Neukum wrote: > Am Dienstag 24 Juli 2007 schrieb Ron Gage: > >> Anyhow, the device appears to require a non-standard function code in >> the URB header, code 0019. SnoopyPro (yeah, on Windows) says this >> function code is "Vendor Endpoint". Obviously, there isn't any current >> way to send such a function code with the Linux USB stack. Problem is, >> the device will not accept the data payloads from a control message. It >> > > Please post the trace showing this feature. > > Regards > Oliver > This is a good one to start with as it is seen literally hundreds of times in the trace.
20 in down n/a 3.195 VENDOR_ENDPOINT - URB Header (length: 80) SequenceNumber: 20 Function: 0019 (VENDOR_ENDPOINT) PipeHandle: 00000000 SetupPacket: 0000: 00 81 82 00 00 00 00 00 bmRequestType: 00 DIR: Host-To-Device TYPE: Standard RECIPIENT: Device bRequest: 81 unknown! No TransferBuffer If I had to guess, this packet is acting something like a "get next" type of function. I can make the entire SnoopyPro dump file available if that would help. Ron Gage Westland, MI ------------------------------------------------------------------------- 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
