From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Russell King'" <rmk+lkml@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: serial_core: verify_port() in wrong spot?
Date: Fri, 9 Jun 2006 13:59:13 -0400 [thread overview]
Message-ID: <093501c68bee$6aef1ad0$294b82ce@stuartm> (raw)
In-Reply-To: <20060609162320.GA11997@flint.arm.linux.org.uk>
From: Russell King [rmk@arm.linux.org.uk]
> I'd rather verify_port didn't get used for that - it's purpose is to
> validate changes the admin makes to the port.
I did figure out that's what it's currently used as, but I didn't want
to introduce a whole new call just to verify that the UART has 9bit
capability.
Why aren't user changes validated?
> I don't know why you think that setting 9bit mode should be done this
> way rather than through the usual termios methods - the
> termios methods
> already have a way to control the length of each character,
> so it would
> seem logical to put the control in there.
9bit mode is much more than just words of 9 bit length. Parity is
gone, replaced by the 9th bit; reads and writes have to treat the
buffers driver-side buffers as 16 bit-wide instead of 8-bit; reads and
writes to the hardware are correspondingly different; there are new
interrupts; software flow control is gone; there's special address
matching and a new ioctl to set that up.
It seemed easier to create a new mode of operation based on the
UPF_9BIT flag; using the CS9 flag doesn't imply any of the above
except for 9 bit length.
However, I'm open to having my mind changed.
..Stu
next prev parent reply other threads:[~2006-06-09 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 14:52 serial_core: verify_port() in wrong spot? Stuart MacDonald
2006-06-09 16:23 ` Russell King
2006-06-09 17:59 ` Stuart MacDonald [this message]
2006-06-14 15:33 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 15:56 Stuart MacDonald
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='093501c68bee$6aef1ad0$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.