On Fri, 27 Jun 1997, Ken Nakata wrote:

> On Fri, 27 Jun 1997 17:34:29 -0700 (PDT),
> wrstuden@loki.stanford.edu (Bill Studenmund) wrote:
> > > 
> > > Fcs stands for Frame Check Sequence.  A fancy name for a CRC.  So, I'd
> > > guess the PB can't quite keep up with the data rate thus drops a char
> > > here and there, making discripancies between calculated and received
> > > fcs.
> > 
> > I'd bet the error's in the cable. If we were dropping characters,
> > we'd generate fifo or ring overflows too. Or is logging set to
> > ignore them?
> 
> Yeah, you're absolutely right!  But then again, the question is,
> does the same cable work under MacOS, or anything other than pppd?

Well, the cables work fine for printers, MIDI interfaces, etc.  I tried
booting the PowerBook into MacOS, using FreePPP to connect to the MkLinux
box and its stats reported bad frames, too, though I tested FreePPP at
57,600, so the results were more dramatic (like 30+ seconds to connect to
the computer at the other end of the link by telnet....)

So that pretty much means that it's not the NetBSD driver, or at least
that it's not _just_ the NetBSD driver.  I assume the MacOS serial driver
_does_ tell the other end to wait....  :-)  So it looks like Linux ignores
it even when it does.  Hmmm.


David

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++++>$ UBLAS*++++>$
P+?>$ L+++>$ !E--- W+++>$ N++(+++)>+++$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t+++>$ 5+>++++$ !X- !R tv+>$
b++>$ !DI !D- G++(+++)>$ e>++++ h--! r--- !y-
------END GEEK CODE BLOCK------