From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stuart MacDonald <stuartm@connecttech.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org
Subject: RE: Serial custom speed deprecated?
Date: Thu, 24 Aug 2006 14:03:30 +0100 [thread overview]
Message-ID: <1156424610.3012.29.camel@pmac.infradead.org> (raw)
In-Reply-To: <1156425568.3007.138.camel@localhost.localdomain>
On Thu, 2006-08-24 at 14:19 +0100, Alan Cox wrote:
> Actually to do this right we have to make a decision or two
>
> The POSIX way of handling this requires the speeds are in the termios
> structure "somewhere". We can't easily implement cfgetispeed/cfgetospeed
> unless we grow the termios structure in the kernel and issue 3 new
> ioctls (keeping the others as trivial translations) and then bumping
> glibc and the kernel to do the right thing.
>
> The alternative is that we provide an extra pair of speed ioctls and
> glibc does the magic to hide this lot while providing a termios with the
> new fields itself.
>
> Whichever way we go glibc already has the fields present and the
> libc<->application API appears to be unchanged by this.
>
> I'd rather we went the way of extending our termios to include c_ispeed,
> c_ospeed values. The code isn't hard for the remapping of the old ones
> and it avoids extra ioctls and the corner case races between two speed
> sets that occur if they are two ioctls.
Agreed. Some architectures have c_[io]speed in their struct termios
already, in fact, but others would need new ioctls for it.
--
dwmw2
next prev parent reply other threads:[~2006-08-24 13:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 21:41 Stuart MacDonald
2006-08-24 9:18 ` David Woodhouse
2006-08-24 12:41 ` Stuart MacDonald
2006-08-24 13:19 ` Alan Cox
2006-08-24 13:03 ` David Woodhouse [this message]
2006-08-24 16:27 ` Krzysztof Halasa
2006-08-24 17:41 ` Alan Cox
2006-08-24 18:51 ` Krzysztof Halasa
2006-08-24 20:43 ` linux-os (Dick Johnson)
2006-08-24 22:11 ` Alan Cox
2006-08-27 6:52 ` Rogier Wolff
2006-08-27 10:00 ` Russell King
2006-08-28 14:14 ` Stuart MacDonald
2006-08-28 20:09 ` Russell King
2006-08-29 6:20 ` Rogier Wolff
2006-08-29 7:46 ` Russell King
2006-08-25 15:17 ` Stuart MacDonald
2006-08-25 15:52 ` linux-os (Dick Johnson)
2006-08-24 22:43 ` Alan Cox
2006-08-25 10:58 ` Krzysztof Halasa
2006-08-25 15:21 ` Stuart MacDonald
2006-08-25 19:32 ` Russell King
2006-08-25 20:21 ` Stuart MacDonald
2006-08-25 20:54 ` linux-os (Dick Johnson)
2006-08-25 20:39 ` Theodore Tso
2006-08-26 12:16 ` Krzysztof Halasa
2006-08-25 15:10 ` Stuart MacDonald
2006-08-24 22:05 ` Russell King
2006-08-25 15:01 ` Stuart MacDonald
[not found] <6N8LR-22A-5@gated-at.bofh.it>
[not found] ` <6Njxz-797-13@gated-at.bofh.it>
[not found] ` <6NqfR-5Ld-49@gated-at.bofh.it>
[not found] ` <6NrbQ-7Ab-27@gated-at.bofh.it>
[not found] ` <6NsB4-2GL-37@gated-at.bofh.it>
[not found] ` <6NvSc-1go-31@gated-at.bofh.it>
2006-08-25 11:40 ` Nick Craig-Wood
2006-08-26 18:16 linux
2006-08-26 19:37 ` Ian Stirling
2006-08-26 20:30 ` linux
2006-08-28 12:17 ` linux-os (Dick Johnson)
2006-08-28 14:39 ` Alan Cox
2006-08-28 14:50 ` linux-os (Dick Johnson)
2006-08-28 15:51 ` Michael Poole
2006-08-28 16:57 ` linux-os (Dick Johnson)
2006-08-28 17:40 ` Michael Poole
2006-08-28 18:04 ` linux-os (Dick Johnson)
2006-08-28 17:01 ` Alan Cox
2006-08-28 17:24 ` linux
2006-08-26 19:35 linux
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=1156424610.3012.29.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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
all inboxes | Powered by JetHome®