From: "Ted Ts'o" <tytso@mit.edu>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"John G. Heim" <jheim@math.wisc.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: speakup bug
Date: Sat, 3 Mar 2012 19:41:16 -0500 [thread overview]
Message-ID: <20120304004116.GA3042@thunk.org> (raw)
In-Reply-To: <20120304002111.GP4180@type.famille.thibault.fr>
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
next prev parent reply other threads:[~2012-03-04 0:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 17:18 speakup bug John G. Heim
2012-03-03 17:39 ` Alan Cox
2012-03-03 22:01 ` Ted Ts'o
2012-03-04 0:01 ` John G. Heim
2012-03-04 0:18 ` Samuel Thibault
2012-03-04 0:21 ` Samuel Thibault
2012-03-04 0:41 ` Ted Ts'o [this message]
2012-03-04 0:43 ` Samuel Thibault
2012-03-04 0:44 ` Samuel Thibault
2012-03-04 1:41 ` Ted Ts'o
2012-03-04 0:26 ` Ted Ts'o
2012-03-04 2:03 ` John G. Heim
2012-03-04 21:06 ` Alan Cox
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=20120304004116.GA3042@thunk.org \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jheim@math.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.