From: Hannes Reinecke <hare@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Vojtech Pawlik <vojtech@suse.cz>
Subject: [PATCH 0/2] Remove input_call_hotplug
Date: Tue, 18 Jan 2005 15:56:35 +0100 [thread overview]
Message-ID: <41ED23A3.5020404@suse.de> (raw)
Hi all,
the input subsystem is using call_usermodehelper directly, which breaks
all sorts of assertions especially when using udev.
And it's definitely going to fail once someone is trying to use netlink
messages for hotplug event delivery.
To remedy this I've implemented a new sysfs class 'input_device' which
is a representation of 'struct input_dev'. So each device listed in
'/proc/bus/input/devices' gets a class device associated with it.
And we'll get proper hotplug events for each input_device which can be
handled by udev accordingly.
Drawback is that a new event type (the said 'input_device') is added, so
that hotplug scripts and udev might need to be adapted to handle it
properly. And each device driver needs to be touched to write something
meaningful as the class_id. A fallback is provided, but by neccessity is
not very informative.
Patch 1/2 implements the core changes to drivers/input/input.c
Patch 2/2 provides proper device names for input drivers.
Patches are relative to bk://kernel.bkbits.net/vojtech/input
Comments are welcome.
Please CC me directly as I'm not on this list.
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
next reply other threads:[~2005-01-18 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 14:56 Hannes Reinecke [this message]
2005-01-18 21:30 ` [PATCH 0/2] Remove input_call_hotplug Greg KH
2005-01-18 21:49 ` Dmitry Torokhov
2005-01-18 21:58 ` Greg KH
2005-01-18 22:20 ` Dmitry Torokhov
2005-01-19 1:31 ` Greg KH
2005-01-19 11:56 ` Hannes Reinecke
2005-01-19 14:30 ` Dmitry Torokhov
2005-01-19 21:39 ` Greg KH
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=41ED23A3.5020404@suse.de \
--to=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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