From: "Richard B. Johnson" <root@chaos.analogic.com>
To: henrique.gobbi@cyclades.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interpretation of termios flags on a serial driver
Date: Wed, 26 Mar 2003 18:18:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0303261804020.2833@chaos> (raw)
In-Reply-To: <3E81BE5C.400@cyclades.com>
On Wed, 26 Mar 2003, Henrique Gobbi wrote:
> Hi,
>
> If this is not the right forum to discuss this matter, excuse me. Please
> point me to the right place.
>
> I'm having some problems understanding three flags on the termios
> struct: PARENB, INPCK, IGNPAR. After reading the termios manual a couple
> of times I'm still not able to understand the different purposes of
> these flags.
>
> What I understood:
>
> 1 - PARENB: if this flag is set the serial chip must generate parity
> (odd or even depending on the flag PARODD). If this flag is not set, use
> parity none.
>
> 2 - IGNPAR: two cases here:
> 2.1 - PARENB is set: if IGNPAR is set the driver should ignore all
> parity and framing errors and send the problematic bytes to tty flip
> buffer as normal data. If this flag is not set the driver must send the
> problematic data to the tty as problematic data.
>
> 2.2 - PARENB is not set: disregard IGNPAR
>
> What I don't understand:
>
> 3 - Did I really understand the items 1 and 2 ?
>
> 4 - INPCK flag: What's the purpose of this flag. What's the diference in
> relation to IGNPAR;
>
> 5 - If the TTY knows the data status (PARITY, FRAMING, OVERRUN, NORMAL),
> why the driver has to deal with the flag IGNPAR. Shouldn't the TTY being
> doing it ?
>
> Thanks in advance
> Henrique
>
Since I've been mucking with serial I/O for many years, I'll
explain what I've descovered.
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.
INPCK used to tell the driver to echo the rubout charcter
every time you got a parity error. This would cause the
user to back-space over the rubout character and enter the
errored character again. I don't know if Linux actually does
this. This was the "parity-checking" that you are enabling.
With this enabled, the errored character should go into the
buffer so the user can back-space over it.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-03-26 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 0:19 Kernel Boot Speedup Ro0tSiEgE LKML
2003-03-06 0:44 ` Andy Pfiffer
2003-03-06 1:35 ` Adam Sulmicki
2003-03-06 10:01 ` Helge Hafting
2003-03-06 10:40 ` John Bradford
2003-03-26 9:23 ` Daniel Phillips
2003-03-26 14:51 ` Interpretation of termios flags on a serial driver Henrique Gobbi
2003-03-26 23:18 ` Richard B. Johnson [this message]
2003-03-26 15:33 ` Henrique Gobbi
2003-03-27 0:24 ` Russell King
2003-03-27 1:41 ` Richard B. Johnson
2003-03-27 1:01 ` Robert White
2003-03-26 23:33 Ed Vance
2003-03-27 0:17 ` Henrique Gobbi
2003-03-27 0:59 Ed Vance
2003-03-27 16:41 Ed Vance
2003-03-27 17:00 Ed Vance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0303261804020.2833@chaos \
--to=root@chaos.analogic.com \
--cc=henrique.gobbi@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®