Re: evdev fails with Couldn't open mtdev device

2011-07-12 Thread Florian Echtler
On Mon, 2011-07-11 at 16:07 -0700, walt wrote: Have you read about the new InputClass Section? It has some advantages over the older InputDevice, including the important ability to identify devices by their plug-n-play names instead the event number. As an example, here's my input section

Re: evdev fails with Couldn't open mtdev device

2011-07-12 Thread Peter Hutterer
On Tue, Jul 12, 2011 at 01:48:53PM +0200, Florian Echtler wrote: On Mon, 2011-07-11 at 16:07 -0700, walt wrote: Have you read about the new InputClass Section? It has some advantages over the older InputDevice, including the important ability to identify devices by their plug-n-play names

Re: evdev fails with Couldn't open mtdev device

2011-07-12 Thread Peter Hutterer
On Mon, Jul 11, 2011 at 11:24:28AM +0200, Florian Echtler wrote: Hi everyone, I'm trying to configure a secondary X server for an auxiliary touchscreen, but I'm having some problems with the input configuration. To keep input for my main screen and the auxiliary screen separate, I'm using

Re: evdev fails with Couldn't open mtdev device

2011-07-11 Thread walt
On 07/11/2011 02:24 AM, Florian Echtler wrote: Hi everyone, I'm trying to configure a secondary X server for an auxiliary touchscreen, but I'm having some problems with the input configuration. To keep input for my main screen and the auxiliary screen separate, I'm using the following