Messages in this thread | | | Date | Sat, 6 Sep 2003 09:38:16 +0200 | From | Jan-Benedict Glaw <> | Subject | Re: [linux-usb-devel] 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter |
| |
On Fri, 2003-09-05 16:08:52 -0700, Greg KH <greg@kroah.com> wrote in message <20030905230852.GA18196@kroah.com>: > 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.
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...
MfG, JBG
-- Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA)); [unhandled content-type:application/pgp-signature] | |