Spotted what is (to me) a regression under 2.6.31 (showed up in .0, still present in .4) Symptoms: FTDI device stops working. In this case, it is a FTDI on a custom board (which will make reproducing this bug a joy for anyone else, I'm sure). The board talks via a Python client, which sets the board to 115200bps, parity none, then sets DTR to 0, at which point it expects to see several bytes of data from the device. Under 2.6.30 and below this works fine, under 2.6.31 this stalls and gets no data reported from the device. The code in question uses pyserial. The 2.6.30 ftdi_sio under 2.6.31 (surprisingly) still builds, and restores the device functionality, so it's not likely anything outside of the ftdi module itself, looking at the diffs didn't cause any A-Ha moments for me but I don't know much about the USB drivers. Device info: usb 2-1.2: new full speed USB device using ehci_hcd and address 13 usb 2-1.2: New USB device found, idVendor=0403, idProduct=6001 usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1.2: Product: FT232R USB UART usb 2-1.2: Manufacturer: FTDI usb 2-1.2: SerialNumber: A7005hik usb 2-1.2: configuration #1 chosen from 1 choice ftdi_sio 2-1.2:1.0: FTDI USB Serial Device converter detected usb 2-1.2: Detected FT232RL usb 2-1.2: FTDI USB Serial Device converter now attached to ttyUSB1 Bus 002 Device 013: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC I'm not on the usb list, so please CC if I can do any additional testing. -m -- Mike Kershaw/Dragorn <dragorn@xxxxxxxxxxxxxxxxxx> GPG Fingerprint: 3546 89DF 3C9D ED80 3381 A661 D7B2 8822 738B BDB1 "Every time I read this kind of nonsense, I have a mental image of our government -- from city level on up -- as a strung-out derelict curled up in a fetal position in a corner, screaming about the spiders all over him as he clutches a bottle of cheap fortified wine cut with paint thinner."
Attachment:
pgpj76PJoQ8SW.pgp
Description: PGP signature
