All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique Gobbi <henrique2.gobbi@cyclades.com>
To: linux-kernel@vger.kernel.org
Subject: Interpretation of termios flags on a serial driver
Date: Wed, 26 Mar 2003 14:51:08 +0000	[thread overview]
Message-ID: <3E81BE5C.400@cyclades.com> (raw)
In-Reply-To: 20030326092010.3EDA8124023@mx12.arcor-online.net

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


  reply	other threads:[~2003-03-26 22:41 UTC|newest]

Thread overview: 18+ 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   ` Henrique Gobbi [this message]
2003-03-26 23:18     ` Interpretation of termios flags on a serial driver Richard B. Johnson
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
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 23:33 Ed Vance
2003-03-27  0:17 ` Henrique Gobbi
2003-03-27  0:59 Ed Vance
2003-03-27 19:06 ` David Lawyer
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=3E81BE5C.400@cyclades.com \
    --to=henrique2.gobbi@cyclades.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.