From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-input <linux-input@vger.kernel.org>
Subject: new modular hid?
Date: Mon, 12 Jan 2009 23:05:09 +0300 [thread overview]
Message-ID: <496BA275.1080504@msgid.tls.msk.ru> (raw)
Hello.
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...
Thanks!
/mjt
next reply other threads:[~2009-01-12 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 20:05 Michael Tokarev [this message]
2009-01-12 23:54 ` new modular hid? Jiri Kosina
2009-01-13 5:43 ` Dmitry Torokhov
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=496BA275.1080504@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-input@vger.kernel.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.