All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Karel Kulhavý" <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: AT Keyboard (was: Helge Hafting vs. make menuconfig help)
Date: Tue, 15 Jun 2004 17:46:51 +0000	[thread overview]
Message-ID: <20040615174651.A6965@beton.cybernet.src> (raw)
In-Reply-To: <20040615173210.GM20632@lug-owl.de>; from jbglaw@lug-owl.de on Tue, Jun 15, 2004 at 07:32:10PM +0200

> 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.

Cl<

  reply	other threads:[~2004-06-15 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 14:02 Helge Hafting vs. make menuconfig help Karel Kulhavý
2004-06-15 14:10 ` Jan-Benedict Glaw
2004-06-15 14:20   ` Karel Kulhavý
2004-06-15 14:41     ` Jan-Benedict Glaw
2004-06-15 17:21       ` Karel Kulhavý
2004-06-15 17:32         ` Jan-Benedict Glaw
2004-06-15 17:46           ` Karel Kulhavý [this message]
2004-06-15 18:37             ` AT Keyboard (was: Helge Hafting vs. make menuconfig help) Helge Hafting
2004-06-15 19:59               ` Karel Kulhavý
2004-06-15 20:13                 ` Jan-Benedict Glaw
2004-06-16 22:30                 ` Helge Hafting
2004-06-15 20:35 ` Helge Hafting vs. make menuconfig help Vojtech Pavlik

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=20040615174651.A6965@beton.cybernet.src \
    --to=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.