From: Pavel Machek <pavel@ucw.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Jan Engelhardt <jengelh@computergmbh.de>,
linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Console keyboard events and accessibility
Date: Sat, 1 Sep 2007 12:32:58 +0000 [thread overview]
Message-ID: <20070901123258.GA4612@ucw.cz> (raw)
In-Reply-To: <20070901122604.GA3251@implementation.famille.thibault.fr>
> > > > They can use the raw xlation for that.
> > >
> > > For userland, yes. This is for kernel modules.
> >
> > And should speakup be a kernel module? Why?
>
> Because userland only begins quite late in the boot process, and
> userland may hang.
Initrd means userland is started very early on most machines these
days, and kernel may hang, too.
> > What is missing? Yes, you may want to do a small kernel module to read
> > kernel bootup messages.
>
> That's what it's all about.
But this small module should not need keyboard leds support, as those are not used during
boot. If all you want is to read kernel bootup messages, you should
just register a special console. Actually serial console should do.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-09-01 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 0:57 [PATCH] Console keyboard events and accessibility Samuel Thibault
2007-08-21 20:02 ` Andrew Morton
2007-08-21 20:22 ` Samuel Thibault
2007-08-25 1:07 ` Adrian Bunk
2007-08-27 14:59 ` Samuel Thibault
2007-08-21 20:42 ` Jan Engelhardt
2007-08-21 20:49 ` Samuel Thibault
2007-07-12 19:19 ` Pavel Machek
2007-09-01 12:26 ` Samuel Thibault
2007-09-01 12:32 ` Pavel Machek [this message]
2007-09-01 12:51 ` Samuel Thibault
2007-09-01 17:23 ` Pavel Machek
2007-09-01 17:33 ` Samuel Thibault
2007-09-01 18:18 ` Pavel Machek
2007-09-01 19:36 ` Samuel Thibault
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=20070901123258.GA4612@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=jengelh@computergmbh.de \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).