From: John Bradford <john@grabjohn.com>
To: vojtech@suse.cz (Vojtech Pavlik)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Corrected] Set2 scancodes for Japanese keyboard
Date: Sat, 25 Jan 2003 17:37:38 +0000 (GMT) [thread overview]
Message-ID: <200301251737.h0PHbcZY001157@darkstar.example.net> (raw)
In-Reply-To: <20030125183001.F16711@ucw.cz> from "Vojtech Pavlik" at Jan 25, 2003 06:30:01 PM
>
> On Sat, Jan 25, 2003 at 05:28:25PM +0000, John Bradford wrote:
>
> > Some got missed off the first time:
>
> What kernel this is tested with? What method used? These don't look like
> Set2 codes AT ALL.
The kernel is 2.4.20. The keycode is the output from showkey, and the
make and break codes are the output from showkey -s.
Should I have used I8042_DEBUG_IO instead? :-/
John.
next prev parent reply other threads:[~2003-01-25 17:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:14 [PATCH 2.5.59] support japanese JP106 keyboard on new console Hiroshi Miura
2003-01-24 5:57 ` Vojtech Pavlik
2003-01-24 17:03 ` Osamu Tomita
2003-01-25 10:33 ` Vojtech Pavlik
2003-01-25 10:51 ` John Bradford
2003-01-25 11:01 ` Vojtech Pavlik
2003-01-25 13:10 ` John Bradford
2003-01-25 13:15 ` Vojtech Pavlik
2003-01-25 17:20 ` Set2 scancodes for Japanese keyboard John Bradford
2003-01-25 17:28 ` [Corrected] " John Bradford
2003-01-25 17:30 ` Vojtech Pavlik
2003-01-25 17:37 ` John Bradford [this message]
2003-01-25 17:40 ` Vojtech Pavlik
2003-01-25 17:46 ` John Bradford
2003-01-25 19:48 ` Andries Brouwer
2003-01-25 19:54 ` Vojtech Pavlik
2003-01-27 16:35 ` Set3 " John Bradford
2003-01-25 15:29 ` [PATCH 2.5.59] support japanese JP106 keyboard on new console Osamu Tomita
2003-01-25 15:36 ` Vojtech Pavlik
2003-01-24 17:17 ` Osamu Tomita
2003-02-01 1:54 ` Hiroshi Miura
2003-02-02 8:23 ` Vojtech Pavlik
2003-02-02 10:38 ` John Bradford
2003-02-02 10:47 ` Vojtech Pavlik
2003-02-05 3:36 ` Hiroshi Miura
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=200301251737.h0PHbcZY001157@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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