From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: questions about keyboard
Date: Thu, 15 Apr 2004 10:36:09 +0200 [thread overview]
Message-ID: <20040415083609.GU630@lug-owl.de> (raw)
In-Reply-To: <F71A246055866844B66AFEB10654E7860F1B0D@riv-exchb6.echostar.com>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
On Wed, 2004-04-14 14:56:20 -0600, Xu, Jiang <Jiang.Xu@echostar.com>
wrote in message <F71A246055866844B66AFEB10654E7860F1B0D@riv-exchb6.echostar.com>:
> 2. In the application, how can I know which input/event# the usb keyboard
> connects to?
You don't. You can
- Hope that your keyboard is the one and only device...
- Read /proc/bus/input/devices - there should be a "kbd" handler
in the "H: " section
- select() on all event* devices and just only process
keypresses generated from "normal" keys.
> 3. Is there some reference documents about how to read things from
> input/event# ? I mean such as how to read key event?
I don't think there's really good docu available, but it's really
simple. Just open all devices, select() until there's data available (or
just call a blocking read() on it). Something like this should work, but
you'd better add error checking to the open() call...
#include <linux/input.h>
ssize_t ret;
struct input_event my_input;
int fd;
fd = open ("/dev/input/event0", O_RDONLY);
for (;;) {
ret = read (fd, &my_input, sizeof (my_input));
if (ret != sizeof (my_input)
break;
if (my_input.type != EV_KEY)
continue;
/* my_input.code and my_input.type now contain the key and
press/release state; refer to the #defines in linux/input.h
for the mapping .code -> ASCII value */
}
close (fd);
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-15 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:56 questions about keyboard Xu, Jiang
2004-04-15 8:36 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 20:44 Xu, Jiang
2004-04-15 20:08 Xu, Jiang
2004-04-15 20:22 ` Jan-Benedict Glaw
2004-04-14 20:31 Xu, Jiang
2004-04-14 20:36 ` Geert Uytterhoeven
2004-04-14 20:18 Xu, Jiang
2004-04-14 20:25 ` Jan-Benedict Glaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040415083609.GU630@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox