From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial_core: verify_port() in wrong spot?
Date: Wed, 14 Jun 2006 16:33:53 +0100 [thread overview]
Message-ID: <20060614153353.GB17432@flint.arm.linux.org.uk> (raw)
In-Reply-To: <093501c68bee$6aef1ad0$294b82ce@stuartm>
On Fri, Jun 09, 2006 at 01:59:13PM -0400, Stuart MacDonald wrote:
> 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?
The only things which users can change is low latency, the alternative
(deprecated) "38400-baud" baud rates, and the custom divisor. None of
these depend on the low level driver, so there's no point asking the
low level driver to validate them.
> 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.
Well, I'll have to read up on this before I can comment any further.
At the moment I don't feel qualified to answer your questions.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-06-14 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 14:52 Stuart MacDonald
2006-06-09 16:23 ` Russell King
2006-06-09 17:59 ` Stuart MacDonald
2006-06-14 15:33 ` Russell King [this message]
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=20060614153353.GB17432@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartm@connecttech.com \
/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
Powered by JetHome