From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: questions about keyboard
Date: Wed, 14 Apr 2004 22:25:34 +0200 [thread overview]
Message-ID: <20040414202534.GS630@lug-owl.de> (raw)
In-Reply-To: <F71A246055866844B66AFEB10654E7860F1B0B@riv-exchb6.echostar.com>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Wed, 2004-04-14 14:18:18 -0600, Xu, Jiang <Jiang.Xu@echostar.com>
wrote in message <F71A246055866844B66AFEB10654E7860F1B0B@riv-exchb6.echostar.com>:
> However, what I don't get is how can I get the key event from the kernel? I
> tried to listen to all the ttyN, but none of them connect to the keyboard.
> I wonder how I can write a user space application that can get the key
> event? Could somebody help me out? Because it is an embedded device, there
> is no X.
Well, one of /dev/tty, /dev/tty0 or /dev/console should work. If you'd
likt to use the new'n'fancy style, use /dev/input/eventX .
MfG, JBG
--
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-14 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:18 questions about keyboard Xu, Jiang
2004-04-14 20:25 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 20:31 Xu, Jiang
2004-04-14 20:36 ` Geert Uytterhoeven
2004-04-14 20:56 Xu, Jiang
2004-04-15 8:36 ` Jan-Benedict Glaw
2004-04-15 20:08 Xu, Jiang
2004-04-15 20:22 ` Jan-Benedict Glaw
2004-04-15 20:44 Xu, Jiang
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=20040414202534.GS630@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