[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m31wr6otlr.fsf@defiant.localdomain>
Date: Thu, 24 Aug 2006 20:51:12 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@...radead.org>,
Stuart MacDonald <stuartm@...necttech.com>,
linux-serial@...r.kernel.org,
"'LKML'" <linux-kernel@...r.kernel.org>
Subject: Re: Serial custom speed deprecated?
Alan Cox <alan@...rguk.ukuu.org.uk> writes:
>> Does that mean that standard things like termios will use:
>> #define B9600 9600
>> #define B19200 19200
>
> That would have been very smart when Linus did Linux 0.12, unfortunately
> he didn't and we've also got no spare bits. Worse still if we exported
> them that way glibc has now way to map new speeds onto the old ones for
> applications.
Hmm... I'm not sure if I understand this correctly. Can't we just
create the 3 new ioctls in the kernel and teach glibc to use it?
The compatibility ioctls would talk to new ioctls only and translate
things. Anything (userspace) wanting non-traditional speeds would
have to use new interface (i.e., be compiled against the new glibc)
and the speeds would show as EXTA or EXTB or something when queried
using old ioctl.
Yes, the binary interface between glibc and userland would change
(with compatibility calls translated by glibc to new ioctls, or to
old ones on older kernels).
The old ioctls would be optional in the kernel (and perhaps in glibc,
sometime).
Not sure if we want int, uint, or long long for speed values :-)
--
Krzysztof Halasa
-
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/
Powered by blists - more mailing lists