* Re: Hotplugs and [input] dev links.
@ 2001-01-17 17:08 David Brownell
0 siblings, 0 replies; only message in thread
From: David Brownell @ 2001-01-17 17:08 UTC (permalink / raw)
To: linux-hotplug
> I believe that it's the job of the hotplug system to do the links
> dynamically from (openned)/dev/(usb|input)/device to /dev/device, like
> cardmgr do for /dev/modem.
I'm not so sure that's even desirable. But wouldn't that
be a job for "devfsd", if it were?
> The problem is that i don't see no ways to
> detect where the devices has been openned.
You mean "device has been connected", right?
> For example if i have a (usb) mouse and a (usb) keyboard, if i load
> the mousedev and usbmouse i get the mouse working on :
>
> /dev/input/mouse0
>
> if i load before the keyboard i get the keyboard on /dev/input/mouse0 and after
> the mouse on /dev/input/mouse1, so how could we get an information
> where to setup the link ?
>
> [Maybe it should be Cc'ed to usb-devel]
If this is your combined keyboard/mouse device, I'm not sure I see
what the problem is. /dev/input/mice should handle things.
- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-01-17 17:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-01-17 17:08 Hotplugs and [input] dev links David Brownell
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.