From: Andries Brouwer <aebr@win.tue.nl>
To: junkio@cox.net
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.0-test1 JAP_86 disappeared from atkbd.c
Date: Sat, 19 Jul 2003 18:12:05 +0200 [thread overview]
Message-ID: <20030719181205.A3543@pclin040.win.tue.nl> (raw)
In-Reply-To: <7vy8yudcec.fsf@assigned-by-dhcp.cox.net>; from junkio@cox.net on Sat, Jul 19, 2003 at 03:44:11AM -0700
On Sat, Jul 19, 2003 at 03:44:11AM -0700, junkio@cox.net wrote:
> In 2.4, Japanese 86/106 keyboards used to be able to generate
> backslash and pipe characters (around ll. 367 in
> linux-2.4.21/drivers/char/pc_keyb.c), but the rewritten AT
> keyboard driver linux-2.6.0-test1/drivers/input/keyboard/atkbd.c
> does not seem to have corresponding support for that key. As a
> result, the key seems to be dead and I cannot type '|' on such a
> keyboard from Linux console (it works OK in X Window but that is
> expected).
>
> For your reference, here is some comments in the 2.4 PC keyboard
> driver that I think is relevant.
>
> ...
> } else if (scancode >= SC_LIM) {
> /* This happens with the FOCUS 9000 keyboard
> Its keys PF1..PF12 are reported to generate
> 55 73 77 78 79 7a 7b 7c 74 7e 6d 6f
> Moreover, unless repeated, they do not generate
> key-down events, so we have to zero up_flag below */
> /* Also, Japanese 86/106 keyboards are reported to
> generate 0x73 and 0x7d for \ - and \ | respectively. */
> /* Also, some Brazilian keyboard is reported to produce
> 0x73 and 0x7e for \ ? and KP-dot, respectively. */
>
> *keycode = high_keys[scancode - SC_LIM];
>
> ...
Ha - really long ago I wrote that..
Yes, for 2.5 things are much more involved, but I suppose that
all will be well if you add the line
keycode 183 = backslash bar
to your keymap.
Andries
next prev parent reply other threads:[~2003-07-19 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 10:44 [BUG] 2.6.0-test1 JAP_86 disappeared from atkbd.c junkio
2003-07-19 16:12 ` Andries Brouwer [this message]
2003-07-20 20:53 ` junkio
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=20030719181205.A3543@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=junkio@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).