From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'Krzysztof Halasa'" <khc@pm.waw.pl>
Cc: "'David Woodhouse'" <dwmw2@infradead.org>,
<linux-serial@vger.kernel.org>,
"'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: Serial custom speed deprecated?
Date: Fri, 25 Aug 2006 11:01:38 -0400 [thread overview]
Message-ID: <043201c6c857$5ddd6c20$294b82ce@stuartm> (raw)
In-Reply-To: <1156441293.3007.184.camel@localhost.localdomain>
From: On Behalf Of Alan Cox
> At this point I think we need
>
> - An ioctl to set/get the actual baud rate input/output
> - Some kind of termios flag to indicate they are being
> used (as we have
> CBAUDEX now). [We could "borrow" the 4Mbit one and dual use it IMHO]
>
> For drivers tty_get_baud_rate would return the actual speed as before.
>
> We would need a driver ->set_speed method for the cases where
> - ioctl is called to set specific board rate
> - OR termios values for tty speed change
> - While we are at it we might want to make ->set_termios also
> allowed to fail
>
> [and if you had no ->set_speed method non standard speeds would be
> refused by the tty layer for back compat]
>
> Anyone got any problems with this before I go and implement it ?
Sounds good.
..Stu
next prev parent reply other threads:[~2006-08-25 15:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 21:41 Serial custom speed deprecated? 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
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 [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
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='043201c6c857$5ddd6c20$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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