linux-os \(Dick Johnson\) writes:
> On Mon, 28 Aug 2006, Michael Poole wrote:
>
>> What baud rate does your system define CBAUDEX | B0 to be? On my
>
> B0 is 0 (zero), no bits. If you are trying to play semantic games and
> claim B0 is 1, i.e., bit 0, then it would not be written as B0, it
> would be written as B(0) or B:0. B0 is defined to be the baud-rate
> used to hang up the modem. It is zero in all bits on most all
> implementations including my Sun. On most recent Linux distributions,
> CBAUDEX is (octal) 0010000. Since B0 is zero, ORing it into CBAUDEX
> does nothing.
Thanks, Sherlock! Again: What does CBAUDEX, by itself, do on your
system? As Alan Cox obviously thought the rest of the world was
bright enough to notice, and as I tried to explain, the CBAUDEX bit is
currently not defined when set by itself (i.e. as if it were CBAUDEX,
CBAUDEX | B0, CBAUDEX << 0 or however else you want to denote it);
there is always some other low-order (CBAUD) bit associated with it:
>> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
