I do turn on CONFIG_VT, if I don't I will not be able to pass compiling the
keyboard.c and some other stuffs.
Because I did not turn on INPUT_EVDEV, so I did not create the device node
However, I just gave it a quick try by turning on INPUT_EVDEV and create the
device nodes; and actually I saw response on input/event0!! Thanks!
Now I have some questions:
1. I have CONFIG_VT on, so why ttyN is not connected to the device? I saw
console.o and tty_io.o, etc.
What may be wrong or did I miss doing some things that I should do?
2. In the application, how can I know which input/event# the usb keyboard
3. Is there some reference documents about how to read things from
input/event# ? I mean such as how to read key event?
From: Geert Uytterhoeven [mailto:firstname.lastname@example.org]
Sent: Wednesday, April 14, 2004 2:37 PM
To: Xu, Jiang
Cc: Linux/MIPS Development
Subject: RE: questions about keyboard
On Wed, 14 Apr 2004, Xu, Jiang wrote:
> Well, this is the problem.
> For some reasons, none of the /dev/tty /dev/tty0... /dev/console is
> connected to the keyboard, I have tried listening all of them. Did I
> configured something wrong? But kernel seems to be getting the key
> event from the keyboard. Another question is if it should connect to
> one of those device nodes, is there anyway I can hack the kernel to
> see where the key event sent to?
Do you have CONFIG_VT=y? I guess not.
Do you receive anything on /dev/input/eventX?
> -----Original Message-----
> From: Jan-Benedict Glaw [mailto:email@example.com]
> Sent: Wednesday, April 14, 2004 2:26 PM
> To: firstname.lastname@example.org
> Subject: Re: questions about keyboard
> On Wed, 2004-04-14 14:18:18 -0600, Xu, Jiang <Jiang.Xu@echostar.com>
> wrote in message
> > 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,
> > 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 .
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like