On Mon, Mar 21, 2011 at 08:30:47PM +0800, Steven Cook wrote: > Hi Rob, > > Thanks for the suggestion but unfortunately it didn't work. > > On 03/20/11 22:26, Robert Pearce wrote: > > > > There was a change to ftdi_sio at 2.6.36 that erroneously set the wrong > > hardware flow control state when flow control is turned off. It's been > > fixed since, but I don't know whether that was included in the first > > 2.6.38 or whether it was patched later. I did a nasty kludge of calling > > > > ioctl ( SerHnd, TIOCMBIS,&value ); > > > > as a work-around when I ran up against this. > I tried all combinations of DTR and RTS with the TIOCMBIS ioctl and > nothing made any difference. I also tried upgrading to 2.6.38-git9 and > that didn't work either. In both cases, the following message is written > repeatedly to the log and read doesn't return. > > Mar 21 20:19:45 stomp kernel: drivers/usb/serial/ftdi_sio.c: > ftdi_process_packet - port 0 This is simply an indication that read is still working as it is printed in the read-urb completion handler. It seems your device is simply not receiving any data, which could suggest that it is indeed DTR/RTS which is causing trouble. > Any other ideas? > > Cheers, > Steve -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
