From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging with current modutils and usbdcvs
Date: Mon, 08 Jan 2001 23:24:59 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97899819010160@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97899764909044@msgid-missing>
> Without usbmodules program the hotplugging didn't work at all for
> scanner (epson perfection 1200u, did work before), nor mouse/joystick
> nor usb-storage.
Curious, it most certainly worked for a mouse I tested it against.
Was that a combined mouse/joystick ... or a real mouse? Did you
install both modutils 2.4.1 and Keith's patch? And then rebuild
and reinstall your kernel, and reinstall all the kernel modules?
Rule of thumb for this version: if a HID device doesn't hotplug,
it's going to need an entry in /etc/hotplug/usb.handmap ... that
will be true until someone starts to teach the "input" subsystem
how to hotplug. (The previous version needed that for usb-storage
devices too ... but the ABI change made it easier for that driver
to hotplug, so usb-storage should mostly hotplug.)
I've not looked at it, but one way to start "input" hotplugging might
be to find out where "hid.c" sees devices' HID descriptors, and issue
call_usermodehelper() with information describing the device type.
An /etc/hotplug/input.agent script should be able to figure out
whether it's a mouse, keyboard, joystick, UPS, tablet, etc and
modprobe accordingly.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-08 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:14 [linux-usb-devel] Re: hotplugging with current modutils and usbdcvs David Brownell
2001-01-08 23:24 ` David Brownell [this message]
2001-01-09 7:22 ` Miles Lane
2001-01-09 7:37 ` Miles Lane
2001-01-09 7:50 ` Norbert Preining
2001-01-09 8:08 ` Miles Lane
2001-01-09 8:18 ` Norbert Preining
2001-01-09 8:18 ` Miles Lane
2001-01-09 8:22 ` Miles Lane
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-97899819010160@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).