From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Clemens Schwaighofer" <cs@tequila.co.jp>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 19:30:04 +0900 [thread overview]
Message-ID: <0e0101c35297$cb1890f0$4fee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 3F20E0ED.6010800@tequila.co.jp
"Clemens Schwaighofer" <cs@tequila.co.jp> wrote:
> cheap, but working and I think it will stay so until 2.6 goes into final
> of distris:
>
> setkeycodes 0x6a 124 1>&2 in your rc.local, local.start or whatever.
> works fine for me for alle 2.5x kernels
There must be a ton of odd stuff going on. "showkey" used to say that the
scan code is 0x7d not 0x6a, but now it displays weird stuff. As previously
mentioned, "getkeycodes" displays a table which seems far removed from
reality. But the patch from junkio@cox.net worked (but "showkey" and
"getkeycodes" still produce weird output).
-- Norman Diamond
next prev parent reply other threads:[~2003-07-25 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 13:56 Japanese keyboards broken in 2.6 Norman Diamond
2003-07-22 15:29 ` Andries Brouwer
2003-07-23 13:14 ` Norman Diamond
2003-07-23 13:38 ` OGAWA Hirofumi
2003-07-24 11:16 ` Hiroshi Miura
2003-07-24 14:26 ` OGAWA Hirofumi
2003-07-25 7:49 ` Clemens Schwaighofer
2003-07-25 10:30 ` Norman Diamond [this message]
2003-07-25 15:42 ` Andries Brouwer
[not found] <fa.jnbj30u.1g6me0g@ifi.uio.no>
[not found] ` <fa.d9tgtm5.1m7agi1@ifi.uio.no>
2003-07-25 1:00 ` junkio
2003-07-25 4:16 ` OGAWA Hirofumi
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 9:27 John Bradford
2003-07-25 16:01 John Bradford
2003-07-25 16:09 ` Andries Brouwer
2003-07-25 16:39 John Bradford
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='0e0101c35297$cb1890f0$4fee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=cs@tequila.co.jp \
--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.