linux-kernel - Re: How to check input device

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]

Message-ID: <alpine.LRH.1.10.0901210007090.13438@twin.jikos.cz>
Date:	Wed, 21 Jan 2009 00:08:25 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	mike zheng <mail4mz@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: How to check input device

On Tue, 20 Jan 2009, mike zheng wrote:

> It is the first time for me to use the input device. I have a keypad 
> driver registers a keypad the device as an input device in the kernel 
> 2.6. The registration of the driver is OK, I can see the interrupt 
> whenever there is key pressed. How can I verify if it works fine? Where 
> can I check keycode value of the key pressed?

If the input device is registered properly, there should be corresponding 
/dev/input/eventX created. Running evtest (from input-utils) on this 
node will decode and dump all the scancodes/keycodes that come out of the 
corresponding input device.

-- 
Jiri Kosina
SUSE Labs

--
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/