[lkml]   [2004]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: AT Keyboard (was: Helge Hafting vs. make menuconfig help)
On Tue, Jun 15, 2004 at 05:46:51PM +0000, Karel Kulhavý wrote:
> > In 2.4.x, the transition from "old-style" input drivers to new-style
> > (Input API) was never finished. Instead, Input API was introduced, and
> > HID devices reported their input to Input API, while old drivers still
> > used all their old ways to deliver their input.
> I (hopefully correctly) assume that one of the old ones is AT keyboard.
> What happens when I press a key on keyboard and the application that
> has the keyboard somehow on it's stdin reads a key? What happens between
> the two events and how does it travel inside the kernel?
> I know how the keys can be read from port 0x60 or whichever.
1. You press the key (on an AT keyboard)
2. The keyboard hardware makes an interrupt
3. The interrupt acitvates the i8042 driver (in 2.6)
which does the port 0x60 stuff.
4. From there, the key is propagated through tty and
console and ends up in your application. This application
might be X, which passes the key onto some program using X.

Helge Hafting

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean