On Fri, Apr 18, 2014 at 04:11:26PM -0700, Larry Baker wrote: > Greg, > > On 18 Apr 2014, at 3:43 PM, Greg KH wrote: > > > On Fri, Apr 18, 2014 at 03:37:53PM -0700, Larry Baker wrote: > >> Greg, > >> > >> Any suggestions how to trace what is going on? > > > > Going on with what? Was there a bug report in that wall of text that I > > missed? :) > > "It sort of works. What happens is, after about 8 or 9 hours, the RX > to the TTY port times out. Sometimes it happens in only an hour, > other times it takes about 14 hours." > > "I am suspicious, for example, that the CTS grant is getting lost." > > Should I report this on the linux-usb@xxxxxxxxxxxxxxx mailing list? Yes, that would be good. But failures like this is going to be hard to track down, as you said, how do you know it's not just the uart in the chip that drops this? These chips are really not meant to be run all the time like this, with constant data streams. They are really cheep chips. I'd go buy a few different types, of different cores, and try to find one that works for your workload. That's going to be the simplest, and probably cheapest, way to do this. best of luck, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
