From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
linux-input <linux-input@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: new modular hid?
Date: Mon, 12 Jan 2009 21:43:44 -0800 [thread overview]
Message-ID: <20090112213924.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.LRH.1.10.0901130052180.24105@twin.jikos.cz>
On Tue, Jan 13, 2009 at 12:54:06AM +0100, Jiri Kosina wrote:
>
> [ added Jiri Slaby to CC ]
>
> On Mon, 12 Jan 2009, Michael Tokarev wrote:
>
> > I tried to run a new (2.6.28) kernel today, to discover that
> > my keyboard does not work anymore. After investigation it
> > turned out the keyboard is now handled by a hid-sub-driver,
> > hid-bright, and it does not work if this (mostly one-liner)
> > driver module is not loaded.
> >
> > udev/m.i.t works fine, it's the initramfs which is broken.
> > I.e., there's no keyboard during initramfs stage, only when
> > udev runs and loads everything - as much as i hate it, it
> > becomes more and more mandatory, but that's another story.
> >
> > Before 2.6.28, I used to include usbhid into initramfs.
> > Now, it's not sufficient anymore.
> >
> > So I've two questions:
> >
> > 1) which drivers to include into ramfs and load for a
> > "generic USB keyboard" to work? Maybe from now on one
> > have to use usbkbd instead of usbhid? I just want to
> > be able to do some rescue stuff before actual system
> > startup in case a system does not boot for whatever
> > reason (root fs is corrupt or wrong raid1 replacement
> > disk or whatever).
> >
> > 2) why all those tiny "subdrivers" in the first place?
> > I looked into several of them, and they're mostly sort
> > of quirks or some additional features or additional key
> > (re)mapping. Why can't it all be done in the main driver
> > instead, just like it is done for PCI bus for example?
> > The amount of real-work code is tiny, modules are much
> > bigger - both the resulting .ko files and all the
> > init/exit wrappers in .c files...
> >
I would agree with Michael here, it looks like we went a bit
overboard with HID quirks. I think sensible solution would be to
merge quirks into 3-4 files (one per device type) and maybe even
compile keyboard quirks into hid core.
Of course if we see that there are big sub-drivers appear we can
still have them split out.
--
Dmitry
next prev parent reply other threads:[~2009-01-13 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 20:05 new modular hid? Michael Tokarev
2009-01-12 23:54 ` Jiri Kosina
2009-01-13 5:43 ` Dmitry Torokhov [this message]
2009-01-13 8:50 ` Jiri Kosina
2009-01-13 9:00 ` Jiri Kosina
2009-01-13 9:08 ` Dmitry Torokhov
2009-01-14 13:26 ` Michael Tokarev
2009-01-14 13:39 ` Jiri Kosina
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=20090112213924.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).