linux-mips
[Top] [All Lists]

Re: questions about keyboard

To: linux-mips@linux-mips.org
Subject: Re: questions about keyboard
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date: Wed, 14 Apr 2004 22:25:34 +0200
In-reply-to: <F71A246055866844B66AFEB10654E7860F1B0B@riv-exchb6.echostar.com>
Mail-followup-to: linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <F71A246055866844B66AFEB10654E7860F1B0B@riv-exchb6.echostar.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.5.1+cvs20040105i
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: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>