linux-kernel - Re: /proc/bus/input/devices changing while booting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 18 Apr 2009 16:36:10 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Stefan Sassenberg <stefan.sassenberg@....de>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: /proc/bus/input/devices changing while booting

Hi Stefan,

On Wed, Mar 25, 2009 at 05:20:56PM +0100, Stefan Sassenberg wrote:
> Hello,
>
> while booting, an init-script on my machine greps the Handlers entry of  
> a certain device (USB touchscreen) from /proc/bus/input/devices. It ends  
> with "event2", so I configure my software to listen for events in  
> /dev/input/event2. A few seconds later /proc/bus/input/devices changes,  
> the order of the devices is different and the Handlers entry for my  
> device ends with event1 making my device misconfigured and thus unusable.
>
> Can anybody explain that behaviour? How can I get the final eventX  
> device file?
>
> I'm using kernel 2.6.28.8 on an Intel Celeron, chipset ICH5.
>

Something causes disconnect of your touchscreen. I think this can happen of 
EHCI is loaded after UHCI/OHCI and they all figure our which devices should be 
driven by whom. Does it help if you compile EHCI in kernel or make sure it 
gets loaded first?

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/