linux-kernel - Re: Early keyboard initialization?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061011133058.d3b03ea7.rdunlap@xenotime.net>
Date:	Wed, 11 Oct 2006 13:30:58 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Andrew Morton <akpm@...l.org>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	Samuel Thibault <samuel.thibault@...-lyon.org>,
	linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>
Subject: Re: Early keyboard initialization?

On Wed, 11 Oct 2006 13:08:32 -0700 Andrew Morton wrote:

> On Sat, 7 Oct 2006 21:58:54 -0400
> Dmitry Torokhov <dtor@...ightbb.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.

Many USB controllers depend on PCI init.

> > 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@...-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.


---
~Randy
-
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/