From: Michael Poole <mdpoole@troilus.org>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux@horizon.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: Serial custom speed deprecated?
Date: Mon, 28 Aug 2006 11:51:40 -0400 [thread overview]
Message-ID: <87lkp8kgdv.fsf@graviton.dyn.troilus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0608281047360.388@chaos.analogic.com> (linux-os@analogic.com's message of "Mon, 28 Aug 2006 10:50:45 -0400")
linux-os \(Dick Johnson\) writes:
> On Mon, 28 Aug 2006, Alan Cox wrote:
>
>> Ar Llu, 2006-08-28 am 08:17 -0400, ysgrifennodd linux-os (Dick Johnson):
>>> On Sat, 26 Aug 2006 linux@horizon.com wrote:
>>>
>>>>> Or we could just add a standardised extra set of speed ioctls, but then
>>>>> we need to decide what occurs if I set the speed and then issue a
>>>>> termios call - does it override or not.
>>>>
>>>> Actually, we're not QUITE out of bits. CBAUDEX | B0 is not taken.
>>>
>>> B0 is not a bit (there are no bits in 0). It won't work.
>>
>> Well that is how it is implemented and everyone else seems happy. If it
>> violates your personal laws of physics you'll just have to cope.
>
> It has nothing to do with 'personal laws of physics'. On all recent
> implementations, B0 is 0, i.e., the absence of any bits set. Therefore,
> there is no observable difference between CBAUDEX and CBAUDEX | B0,
> as shown above. Therefore, as I stated, it won't work.
What baud rate does your system define CBAUDEX | B0 to be? On my
AMD64 machine, both the x86-64 and i386 asm/termbits.h files skip
CBAUDEX -- B38400 is 0000017 and B57600 is 0010001 (CBAUDEX | B50).
The headers do not define any baud rate between those two, either by
rate or by c_cflag value.
Michael Poole
next prev parent reply other threads:[~2006-08-28 15:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-08-26 19:35 linux
[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-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
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
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=87lkp8kgdv.fsf@graviton.dyn.troilus.org \
--to=mdpoole@troilus.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=linux@horizon.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®