On Wed, Mar 26, 2003 at 5:41 PM, Richard B. Johnson wrote:
>
> On Wed, 26 Mar 2003, Henrique Gobbi wrote:
>
> > Thanks for the feedback.
> >
> > > If PARENB is set you generate parity. It is ODD parity if PARODD
> > > is set, otherwise it's EVEN. There is no provision to generate
> > > "stick parity" even though most UARTS will do that. When you
> > > generate parity, you can also ignore parity on received data if
> > > you want. This is the IGNPAR flag.
> >
> > Ok. But, considering the 2 states of the flag IGNPAR, what
> should the
> > driver do with the chars that are receiveid with wrong
> parity, send this
> > data to the TTY with the flag TTY_PARITY or just discard this data ?
> >
> > regards
> > Henrique
> >
>
>
> If the IGNPAR flag is true, you keep the data. You pretend it's
> okay. Ignore parity means just that. Ignore it. You do not flag
> it in any way. This is essential. If you have a 7-bit link and
> somebody is sending you stick-parity, you can still use the data.
>
Hi Richard,
Right idea, wrong flag. ;-)
IGNPAR = 1 discard received data with parity errors. (ignore data)
INPCK = 0 deliver data with parity errors, as is. (ignore error)
See 2.4/drivers/char/n_tty.c:~500
Cheers,
Ed
----------------------------------------------------------------
Ed Vance edv (at) macrolink (dot) com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:28 EST