From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplugging for the input subsystem
Date: Fri, 28 Sep 2001 16:29:36 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100169471408654@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100169001721471@msgid-missing>
> For a long time there was the problem that while upon inserting an USB
> keyboard the HID driver was auto-loaded OK, the mousedev, joydev, etc
> drivers were not.
>
> This patch implements (among other things) hotplugging for the input
> subsystem.
Great to see this patch! Did you submit this to Linus, or are you
waiting for feedback first? And what version of modutils knows
how to emit records for "struct input_device_id" (or is there one?)
via MODULE_DEVICE_TABLE?
> I can provide some docs if it isn't obvious how it works.
I provided skeletal docs on the website, mostly just grubbed from
the invocation of the hotplug agent.
http://linux-hotplug.sourceforge.net/?selected=input
Real explanations of all those bit parameters would be good to have,
from anyone who knows the input subsystem. There's too much
"see the kernel source" there for my taste ... :)
> It'd be nice if someone could add support for this to the hotplug tools.
Yes indeed ... volunteers?
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-09-28 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 13:07 Hotplugging for the input subsystem Vojtech Pavlik
2001-09-28 16:29 ` David Brownell [this message]
2001-09-28 18:09 ` Vojtech Pavlik
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=marc-linux-hotplug-100169471408654@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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 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).