From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: How usb hotplug works [really: input hotplugging]
Date: Wed, 17 Jan 2001 15:12:46 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97974430824146@msgid-missing> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2347 bytes --]
> I cannot get works actually hotplug with a simple usb keyboard :
Well, it should ... I'll have to verify the latest RPM, to be sure
it still behaves with mine!
On the other hand, that isn't a "simple" keyboard: it has a mouse.
> --=-=-> T: Bus\x02 Lev\x01 Prnt\x02 Port\0 Cnt\x01 Dev#= 3 Spd=1.5 MxCh= 0
> D: Ver= 1.00 Cls\0(>ifc ) Sub\0 Prot\0 MxPS= 8 #Cfgs= 1
> P: Vendor\x05a4 ProdID™98 Rev= 1.00
> S: Manufacturer=NOVATEK
> S: Product=USB Keyboard
> C:* #Ifs= 2 Cfg#= 1 Atr MxPwr\x100mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls\x03(HID ) Sub\x01 Prot\x01 Driver=(none)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That should cause "hid" to be loaded, at least.
Then /etc/hotplug/usb.handmap should add "keybdev" (and input).
Since it seems neither of those happened, I suspect that you
were trying to use a "usbmodules" that doesn't know about the
modutils 2.4.1 output. Or something else broke, and we'd like
to know what.
> E: Ad(I) Atr\x03(Int.) MxPS= 8 Ivl= 10ms
> I: If#= 1 Alt= 0 #EPs= 1 Cls\x03(HID ) Sub\x01 Prot\x02 Driver=(none)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
There are two ways to get that second interface to trigger module
loading: (a) "usbmodules" would figure it out from usbdevfs;
(b) "usb.handmap" can list that specific device. I just updated
"usb.handmap" to know about this funky device.
Assuming Linus merges the usb-storage patch, then the main use for
the "handmap" file is going to be coping with various kinds of
funky HID devices (like this keyboard/mouse combo).
Eventually the input system needs to learn to hotplug. ADB users
need that kind of solution, and device-specific mappings aren't
particularly desirable given how many different HID devices exist.
> i have also to setup a :
>
> post-install usbkbd modprobe keybdev
>
> in my /etc/modules.conf
That seems strange. I thought it was only the HID based driver
which needed the input subsystem and "keybdev". The boot protocol
driver is discouraged for everything except systems with really
constrained resources, it's not as functional.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2001-01-17 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-97974430824146@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).