Messages in this thread | | | Date | Mon, 13 Jun 2005 15:16:57 -0700 | From | Greg KH <> | Subject | Re: Input sysbsystema and hotplug |
| |
On Mon, Jun 13, 2005 at 04:07:51PM -0500, Dmitry Torokhov wrote: > Hi, > > I am trying to convert input systsem to play nicely with sysfs and I am > having trouble with hotplug agent. The old hotplug mechanism was using > "input" as agent/subsystem name, unfortunately I can't simply use "input" > class because when Greg added class_simple support to input handlers > (evdev, mousedev, joydev, etc) he used that name.
Why not? What's wrong with using the existing input class? I was hopeing it would get flushed out into something "real" someday. All you have to do is keep the "dev" stuff in there somewhere and udev will be happy.
> /sys/class/input---input0 > | > |-input1 > | > |-input2 > | > |-mouse---mouse0 > | | > | |-mouse1 > | | > | --mice > | > |-event---event0 > | > |-event1 > | > |-event2 > > where inputX are class devices, mouse and event are subclasses of input > class and mouseX and eventX are again class devices.
Yes, lots of people want class devices to have children. Unfortunatly they don't provide patches with their requests :)
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |