On Mon, Nov 07, 2005 at 08:43:49PM -0800, Greg KH wrote:
>
> The input subsystem moved to handle nested class devices, so udev had to
> change to handle this properly. I bet however Debian does the initial
> population of the /dev tree is messed up somehow, as that is what it
> looks like is happening (event3 I bet is from a USB device that is added
> after init starts?)
>
Nope, it looks like there's some sort of layering/nesting going on:
% cat /sys/class/input/event1/device/description
i8042 Kbd Port
% cat /sys/class/input/event2/device/description
i8042 Aux Port
% cat /sys/class/input/event3/device/description
Synaptics pass-through
.. and the Synaptics driver wants to talk to /dev/input/event2, and
_not_ /dev/input/event3. But the Debian scripts seem to think that
the only thing of value to expose is the /dev/input/event3, the very
top of the stack. /dev/input/event1, and /dev/input/event2 are both
not showing up on my system once a I boot a post-2.6.14 kernel.
> > So this is what I believe Andrew would call "a regression". :-)
>
> I call it a "Debian mess"...
>
Great.... I'll file a bug report to Debian, and hopefully they can
get this mess straightened out before 2.6.15 (and hopefully before
2.6.14-rc1) ships.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
