Re: Input sysbsystema and hotplug

[Hannes Reinecke <hare@suse.de>]

Dmitry Torokhov wrote:
> On Monday 13 June 2005 16:58, Dmitry Torokhov wrote:
>>On Monday 13 June 2005 16:26, Kay Sievers wrote:
>>>On Mon, Jun 13, 2005 at 04:07:51PM -0500, Dmitry Torokhov wrote:
>>>>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. So currently stock
>>>>kernel gets 2 types of hotplug events (from input core and from input
>>>>handlers) with completely different arguments processed by the same
>>>>input agent.
>>>>
>>>>So I guess my question is: is there anyone who uses hotplug events
>>>>for input interface devices (as in mouseX, eventX) as opposed to
>>>>parent input devices (inputX).
>>>Hmm, udev uses it. But, who needs device nodes. :)
>>>
>>Oh, OK. Damn, Andrew will hate us for breaking mouse support yet again :(
>>because there are people (like me) relying on hotplug to load input handlers.
>>First time I booted by new input hotplug kernel I lost my mouse.
>>
>>I wonder should we hack something allowing overriding subsystem name
>>so we could keep the same hotplug agent? Or should we bite teh bullet and
>>change it?
>>
> 
> Any chance we could quickly agree on a new name for hander devices (other
> than "input") and roll out updated udev before the changes get into the
> kernel? For some reason it feels like udev is mmuch quicker moving than
> hotplug...
> 
My original patch used 'input_device' for it.
Would be nice if it could stay.
This way we have the following event sequence:

input_device event (contains all attributes like 'abs', 'ev' etc.)
-> triggers loading of any input modules
   -> creates the proper input devices
input event (contains the 'dev' attribute for udev)

As the main point of the original 'input' event is in fact the device
node creation (we only have max 4 input modules, which isn't that hard
to figure out), I'd vote for keeping the name 'input' for the device
event and use a new event type 'input_device' for the class device.

And yes, we should break compability and come up with a clean
implementation. And as the original input event is an abomination I
don't see the point in keeping compability with a broken interface.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux AG				S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r 
_______________________________________________
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