From: Andrew Morton <akpm@osdl.org>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: Early keyboard initialization?
Date: Wed, 11 Oct 2006 13:08:32 -0700 [thread overview]
Message-ID: <20061011130832.c9e9b4d5.akpm@osdl.org> (raw)
In-Reply-To: <200610072158.55659.dtor@insightbb.com>
On Sat, 7 Oct 2006 21:58:54 -0400
Dmitry Torokhov <dtor@insightbb.com> wrote:
> On Friday 06 October 2006 16:42, Samuel Thibault wrote:
> > Hi,
> >
> > Is there any reason for initializing the input layer and keyboards so
> > late? Since prevents from being able to perform alt-sysrqs early, and
> > blind people who use speakup would like to get early control over the
> > speech. Here is the patch that they use.
> >
It'd be nice to get sysrq working as early as poss.
> It looks like the change will only work for non-USB input devices since
> USB subsystem is initialized much later.
USB is usually modular (isn't it?)
> Greg, is there a reason why USB can't be initialized earlier?
Greg's in hiding.
> Btw, I don't think we need to initialize gameport early and maybe not
> entire input but split off input/keyboard in the same fashion that
> input/serio and input/gameport are split off.
>
> > Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> >
> > --- /usr/src/linux-2.6.18/drivers/Makefile.orig 2006-10-06 11:34:15.000000000 -0400
> > +++ drivers/Makefile 2006-10-06 11:34:15.000000000 -0400
> > @@ -27,6 +27,9 @@
> >
> > obj-y += serial/
> > obj-$(CONFIG_PARPORT) += parport/
> > +obj-$(CONFIG_SERIO) += input/serio/
> > +obj-$(CONFIG_GAMEPORT) += input/gameport/
> > +obj-$(CONFIG_INPUT) += input/
> > obj-y += base/ block/ misc/ mfd/ net/ media/
> > obj-$(CONFIG_NUBUS) += nubus/
> > obj-$(CONFIG_ATM) += atm/
> > @@ -50,9 +53,6 @@
> > obj-$(CONFIG_USB) += usb/
> > obj-$(CONFIG_PCI) += usb/
> > obj-$(CONFIG_USB_GADGET) += usb/gadget/
> > -obj-$(CONFIG_SERIO) += input/serio/
> > -obj-$(CONFIG_GAMEPORT) += input/gameport/
> > -obj-$(CONFIG_INPUT) += input/
> > obj-$(CONFIG_I2O) += message/
> > obj-$(CONFIG_RTC_LIB) += rtc/
> > obj-$(CONFIG_I2C) += i2c/
Anyway, I'll duck this. Samuel, an appropriate way to make this happen
would be to talk Dmitry into a patch, let it cook in his tree for a couple
of months, then merge it into 2.6.20-early.
next prev parent reply other threads:[~2006-10-11 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 20:42 Samuel Thibault
2006-10-08 1:58 ` Dmitry Torokhov
2006-10-11 20:08 ` Andrew Morton [this message]
2006-10-11 20:16 ` Dmitry Torokhov
2006-10-11 20:30 ` Randy Dunlap
2006-10-11 23:13 ` Greg KH
2006-10-12 7:41 ` Giuseppe Bilotta
2006-10-12 8:10 ` Jan Engelhardt
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=20061011130832.c9e9b4d5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dtor@insightbb.com \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®