Re: [Serial 2.5]: packet drop problem (FE ?)

[Russell King <rmk@arm.linux.org.uk>]

On Fri, Nov 08, 2002 at 11:34:18PM +0100, Martin Diehl wrote:
> The next to know is whether irtty_receive_buf() reports any "Framing or 
> parity error"? IIRC with IGNPAR set we should neither get parity nor 
> framing errors reported and it seems this is how serial8250_change_speed()
> deals with ignore_status_mask. But wait - yes, 8250's receive_chars() 
> seems to accept the character,

Correct.

> but set TTY_FRAME anyway.

Only if INPCK is set.  If it's clear, then it will ignore framing and
parity errors.  (Irrespective of this, it will still internally count
them for statistical purposes, just like 2.4 used to.)

However, since INPCK is clear (from the info Jean's already sent) you'll
receive the character a TTY_NORMAL flag, even though the hardware flagged
an error.

> Ok, I think what might happen is you are receiving some kind of IR-noise 
> (maybe environment, maybe reflected, maybe dongle echo) causing bytes with 
> framing errors to get passed to and handled by irtty in one go with the 
> beginning of the first byte(s) from the next incoming frame. Thus we 
> discard the BOF and the whole frame is missed :-(

Maybe the problem is that you want to discard the bad byte (by flagging
it with a non-TTY_NORMAL flag.)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html