linux-kernel - Re: Serial custom speed deprecated?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0608281347500.818@chaos.analogic.com>
Date:	Mon, 28 Aug 2006 14:04:12 -0400
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Michael Poole" <mdpoole@...ilus.org>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>, <linux@...izon.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: Serial custom speed deprecated?

On Mon, 28 Aug 2006, Michael Poole wrote:

> 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:
>

Certainly CBAUDEX does not represent a baud-rate itself. It is
a bit that is used to extend the baud-rate setting from the values
that could fit within the (CBAUD & ~CBAUDEX) mask so B50 through
B38400 could become B57600 through B4000000 when this bit is set.

The confusion arises when you use B0 in your argument. CBAUDEX was
the relevant bit, sufficiently defined, without adding a non-existent
bit.

I am sensitive to 'B0' because any new implementation must also
provide for its functionality. There still are modem-controlled
or connected devices that need to secure a line by hanging up.

>>> 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
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.62 BogoMips).
New book: http://www.AbominableFirebug.com/
_
..

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/