From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: The case of udev and the missing /dev/input/mice
Date: Wed, 21 Sep 2005 15:33:19 +0000 [thread overview]
Message-ID: <d120d50005092108331ad1871d@mail.gmail.com> (raw)
In-Reply-To: <1127270286.10585.14.camel@localhost.localdomain>
On 9/21/05, Greg KH <greg@kroah.com> wrote:
> On Wed, Sep 21, 2005 at 01:19:35PM +0200, Olivier Blin wrote:
> > Kay Sievers <kay.sievers@vrfy.org> writes:
> >
> > > At the time the input layer is fixed, the need for udevsend will
> > > completely go away and /proc/sys/kernel/hotplug should be disabled
> > > when taking over control from the kernel - it is only needed in
> > > initramfs.
> > > After input is fixed, the whole event reordering and timeout handling
> > > will be removed from udevd and we need to start udevd manually anyway.
> >
> > Isn't it fixed now? Or not merged yet?
> > http://lkml.org/lkml/2005/9/15/59
>
> Not merged at all, we still are working on fixing up the driver core to
> handle this properly...
>
I think while driver core is being fixed we should go "Suse way" and
add top-level input_dev class and merge input changes. Hovewer there
will be compatibility issues with current installation (as there will
be compatibility problems once we fix driver core but I'd rather force
users to upgrade once)...
Greg, would you accept a patch that would allow a class override its
subsustem as far as hotplug is concerned? This way "input_dev" class
would set its name to "input" allowing using existing setups.
--
Dmitry
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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
next prev parent reply other threads:[~2005-09-21 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 2:38 The case of udev and the missing /dev/input/mice Scott James Remnant
2005-09-21 9:51 ` Kay Sievers
2005-09-21 11:19 ` Olivier Blin
2005-09-21 12:47 ` Greg KH
2005-09-21 12:53 ` Scott James Remnant
2005-09-21 15:33 ` Dmitry Torokhov [this message]
2005-09-21 15:49 ` Greg KH
2005-09-21 16:00 ` Greg KH
2005-09-21 16:11 ` Dmitry Torokhov
2005-09-21 16:33 ` Greg KH
2005-09-21 16:46 ` Dmitry Torokhov
2005-09-21 17:01 ` Greg KH
2005-09-21 17:12 ` Dmitry Torokhov
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=d120d50005092108331ad1871d@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).