On Wed, Jan 19, 2005 at 02:48:14PM +0100, Hannes Reinecke wrote:That depends on the driver. input_dev is in general a static entry in the driver-dependend structure, which in turn may be statically or dynamically allocated (depending on whether the driver allows for more than one instance of the device to be connected).
Hi Dmitry,
attached is the reworked patch for removing the call to call_usermodehelper from input.c
I've used the 'phys' attribute to generate the device names, this way we don't need to touch all drivers and the patch itself is nice and small.
The main problem of this is the input_dev structures are created
statically, right? Because of this, the release function really doesn't
work out correctly I think....
Other than that this looks a lot better.kewl.
Hm, you're still generating hotplug events with this patch of theOf course. I didn't see another way, as already stated the originial input events were something of a misnomer.
"input_device" type, right?