[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120304004116.GA3042@thunk.org>
Date: Sat, 3 Mar 2012 19:41:16 -0500
From: Ted Ts'o <tytso@....edu>
To: Samuel Thibault <samuel.thibault@...-lyon.org>,
"John G. Heim" <jheim@...h.wisc.edu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org
Subject: Re: speakup bug
On Sun, Mar 04, 2012 at 01:21:11AM +0100, Samuel Thibault wrote:
> Samuel Thibault, le Sun 04 Mar 2012 01:18:06 +0100, a écrit :
> > Just for the record: what we need is being able to open a serial port
> > and read/write from inside the kernel. Using a daemon that does the open
> > and setting up speakup as a line discipline would be possible, but it
> > then depends on / working, and that's not something e.g. administrators
> > can really afford depending on.
>
> BTW: yes, that does not mean that speakup couldn't use a line discipline
> already. Sure, still on the TODO list for years too.
Actualy you *can* open a tty from the kernel. Look at how
/dev/console is opened in kernel_init() in init/main.c. So you could
set up the line discipline out of the kernel if you really wanted to
get the speakup system set up in early boot, as opposed to setting
things up in either the initial ramdisk or in the init scripts.
If you don't even want a dependency on /, life gets a little harder,
but is that really that important? The advantages of doing it cleanly
is that it will work on systems that don't have a normal serial port,
but only have a USB interface (for example, if you were going to try
to hack in support for a mobile device or some other embedded system).
- Ted
--
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