Regarding the use of EVTEST..

[Chase Douglas]

On Tue, 2010-07-13 at 22:57 +0530, Gursimran singh wrote:
> hello i'm Gursimran singh , I have been working on touchpads quite a
> bit now. I want to use evtest to get live events form the touchpad
> using evdev ..Please also suggest some other alternative of this tool
> if that could work for me ..
> 
> This is what happens when I run the command on my terminal after this
> the I have to close the terminal by the cross button and the evtest
> program blocks and do nothing. I hope this is not the normal
> behaviour ..
> 
> simar at simar-laptop:~$ sudo evtest /dev/input/event4
> [sudo] password for simar: 
> Input driver version is 1.0.0
> Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0
> Input device name: "Video Bus"
> Supported events:
>   Event type 0 (Sync)
>   Event type 1 (Key)
>     Event code 224 (Brightness down)
>     Event code 225 (Brightness up)
>     Event code 227 (?)
>     Event code 240 (Unknown)
>     Event code 241 (?)
>     Event code 242 (?)
>     Event code 243 (?)
>     Event code 244 (?)
>     Event code 245 (?)
> Testing ... (interrupt to exit)
> simar at simar-laptop:~$ sudo evtest /dev/input/event9
> [sudo] password for simar: 
> Input driver version is 1.0.0
> Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
> Input device name: "SynPS/2 Synaptics TouchPad"
> Supported events:
>   Event type 0 (Sync)
>   Event type 1 (Key)
>     Event code 272 (LeftBtn)
>     Event code 273 (RightBtn)
>     Event code 274 (MiddleBtn)
>     Event code 325 (ToolFinger)
>     Event code 330 (Touch)
>   Event type 3 (Absolute)
>     Event code 0 (X)
>       Value      1
>       Min     1472
>       Max     5472
>     Event code 1 (Y)
>       Value   5855
>       Min     1408
>       Max     4448
>     Event code 24 (Pressure)
>       Value      0
>       Min        0
>       Max      255
>     Event code 28 (Tool Width)
>       Value      0
>       Min        0
>       Max        0
> Testing ... (interrupt to exit)
> 
> 

The synaptics X input driver grabs the /dev/input/event* device node
such that no other client can see events from it. This prevents you from
being able to use evtest while X is running in the current virtual
terminal (VT). You will need to switch to a VT without X to see
anything.

-- Chase