Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965011AbVKHNOz (ORCPT ); Tue, 8 Nov 2005 08:14:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965025AbVKHNOz (ORCPT ); Tue, 8 Nov 2005 08:14:55 -0500 Received: from thunk.org ([69.25.196.29]:9167 "EHLO thunker.thunk.org") by vger.kernel.org with ESMTP id S965011AbVKHNOy (ORCPT ); Tue, 8 Nov 2005 08:14:54 -0500 Date: Tue, 8 Nov 2005 08:14:51 -0500 From: "Theodore Ts'o" To: Greg KH Cc: linux-kernel@vger.kernel.org Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad Message-ID: <20051108131451.GD6129@thunk.org> Mail-Followup-To: Theodore Ts'o , Greg KH , linux-kernel@vger.kernel.org References: <20051106203421.GB2527@kroah.com> <20051107053648.GA7521@thunk.org> <20051107155243.GA14658@kroah.com> <20051107181706.GB8374@thunk.org> <20051107182434.GC18861@kroah.com> <20051108033019.GA6129@thunk.org> <20051108044348.GB5516@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051108044348.GB5516@kroah.com> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1509 Lines: 41 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/