On Saturday 06 September 2003 15:38, Jan-Benedict Glaw wrote: > On Fri, 2003-09-05 16:08:52 -0700, Greg KH <[EMAIL PROTECTED]> > wrote in message <[EMAIL PROTECTED]>: > > On Wed, Sep 03, 2003 at 02:32:16PM +0800, Michael Frank wrote: > > > On Wednesday 03 September 2003 07:52, Greg KH wrote: > > > Besides it just stopping without obvious reason: > > > > > > 1) It does not like when something is typed on cu and not received by the serial > > > port side > > > connected to PL2303 (CTS low). It tends to hang and the trouble starts.... > > > > > > Sep 3 12:52:15 mhfl2 kernel: ttyUSB0: 1 input overrun(s) > > > Sep 3 12:54:30 mhfl2 last message repeated 2 times > > > > Hm, what is causing this? > > That is probably why cu is getting confused, right? > > I've seen the input overrun message also (with the vanilla driver, not > patched). > It's effect is that the first bytes (maybe up to 100..300 > bytes) are scrambled. It's like accessing a serial link with a horribly > wrong baud rate.
I have seen that too, but rarely. Most the time it hangs after the first few hundred bytes. > > After a split-second, however, everything is okay and I start receiving > valid NMEA data from my GPS receiver. For me, that's not much of a > problem because nmea is checksum'ed and the bad bytes are ignored... > I have used PL2303 so far to grab serial console messages and did not get in synch with cu after the overrun popped up. Regards Michael ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
