public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Congjun Yang <congjuny@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: keyboard raw mode
Date: Sat, 1 Jul 2006 10:04:00 -0400	[thread overview]
Message-ID: <200607011004.01317.dtor@insightbb.com> (raw)
In-Reply-To: <20060701095541.GO26883@lug-owl.de>

On Saturday 01 July 2006 05:55, Jan-Benedict Glaw wrote:
>   * All protocol drivers (eg. the atkbd driver) will *never* ever
>     stuff the raw I/O anywhere.

Actually some of them do via EV_MSC/MSC_RAW events. So raw code should be
available through evdev nodes and also on x86 keyboard driver in raw mode
should also pass raw data through (from atkbd only).

Congjun, what 2.6.x kernel have you tried?

-- 
Dmitry

  reply	other threads:[~2006-07-01 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-01  5:00 keyboard raw mode Congjun Yang
2006-07-01  9:55 ` Jan-Benedict Glaw
2006-07-01 14:04   ` Dmitry Torokhov [this message]
2006-07-02  8:21     ` Congjun Yang
2006-07-02 15:11       ` Dmitry Torokhov
2006-07-03 20:07         ` Congjun Yang

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=200607011004.01317.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=congjuny@yahoo.com \
    --cc=jbglaw@lug-owl.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox