On Thu, 16 Jan 2003, Thomas Chen wrote: | > like you say:v | > | so... if that is the case... from PC/host point of view... we SHOULD | > | never send out any packet that is has OUT bit set???? why am i seeing | > | BULK message being queued up with that bit set ??? | > | | > | 0x80000280 | > | ^ | > | | > | this starts happening when the usbserial being opened... | > | | > | the driver... (SL811) from my reading that look at the PID and decide | > | not to copy the data into the chip's memory area..... | | | but when bit 7 is SET... it means IN ... ??? why is the low | level USB driver getting a packet request with PID = PID_IN ???? | | that was my confusion.... | | the driver is doing | | if (pid != PID_IN) | copy data into the USB chip | | but the packet PID has PID = IN set ????
This is drivers/usb/host/sl*.c, right? Did you trace the call path and value of the <pid> variable there? You can determine that <pid> might be PID_IN, PID_OUT, or PID_SETUP. For PID_OUT and PID_SETUP there is data to write/send on the USB wire to the device. For PID_IN, there is no data. -- ~Randy ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
