public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* /proc/bus/input/devices changing while booting
@ 2009-03-25 16:20 Stefan Sassenberg
  2009-04-18 23:36 ` Dmitry Torokhov
  0 siblings, 1 reply; 2+ messages in thread
From: Stefan Sassenberg @ 2009-03-25 16:20 UTC (permalink / raw)
  To: LKML

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.

Regards

Stefan

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: /proc/bus/input/devices changing while booting
  2009-03-25 16:20 /proc/bus/input/devices changing while booting Stefan Sassenberg
@ 2009-04-18 23:36 ` Dmitry Torokhov
  0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Torokhov @ 2009-04-18 23:36 UTC (permalink / raw)
  To: Stefan Sassenberg; +Cc: LKML

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-04-18 23:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-25 16:20 /proc/bus/input/devices changing while booting Stefan Sassenberg
2009-04-18 23:36 ` Dmitry Torokhov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox