From: Greg KH <greg@kroah.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mousedev auto load on 2.6.14-rc{2,3}
Date: Thu, 1 Dec 2005 13:50:17 -0800 [thread overview]
Message-ID: <20051201215017.GB22439@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0512011641360.32444@gandalf.stny.rr.com>
On Thu, Dec 01, 2005 at 04:46:14PM -0500, Steven Rostedt wrote:
> On Thu, 1 Dec 2005, Greg KH wrote:
>
> > On Thu, Dec 01, 2005 at 02:20:18PM -0500, Steven Rostedt wrote:
> > > Hi,
> > >
> > > Using the same config between 2.6.14 and 2.6.15-rc2 (and with rc3,
> > > haven't tried rc4). The mousedev gets auto loaded on 2.6.14 but does not
> > > with 2.6.15-rc{2,3}. Did something change to prevent the auto loading
> > > of mousedev?
> >
> > This needs to be a FAQ somewhere. This is a known bug in Debian's
> > hotplug/udev package that is being worked on.
> >
> > It's not a kernel bug, but a userspace one. Other distros do not have
> > this issue, perhaps I could recommend a different one for you? :)
> >
>
> Actually, I never said it was a kernel bug :)
>
> I was just wondering what changed between 2.6.14 and 2.6.15-rc2 to break
> debian's hotplug/udev packages.
The input core changed the way it exports its information in sysfs. Now
it properly shows the heirachy of input devices (look at the difference
in /sys/class/input in 2.6.14 and 2.6.15-rc2.) A recent version of udev
is required to be updated to handle this properly, but if you are on
unstable, you should already have that change.
Hope this helps explain things.
greg k-h
next prev parent reply other threads:[~2005-12-01 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 19:20 mousedev auto load on 2.6.14-rc{2,3} Steven Rostedt
2005-12-01 21:34 ` Greg KH
2005-12-01 21:46 ` Steven Rostedt
2005-12-01 21:50 ` Greg KH [this message]
2005-12-01 21:57 ` Steven Rostedt
2005-12-01 21:51 ` Steven Rostedt
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=20051201215017.GB22439@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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