From: junkio@cox.net
To: Andries Brouwer <aebr@win.tue.nl>
Cc: junkio@cox.net, Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.0-test1 JAP_86 disappeared from atkbd.c
Date: Sun, 20 Jul 2003 13:53:08 -0700 [thread overview]
Message-ID: <7vhe5grkcr.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20030719181205.A3543@pclin040.win.tue.nl> (Andries Brouwer's message of "Sat, 19 Jul 2003 18:12:05 +0200")
>>>>> "AB" == Andries Brouwer <aebr@win.tue.nl> writes:
AB> Ha - really long ago I wrote that..
AB> Yes, for 2.5 things are much more involved, but I suppose that
AB> all will be well if you add the line
AB> keycode 183 = backslash bar
AB> to your keymap.
Thanks, it really was a long ago. With the above included in
drivers/char/defkeymap.map and regenerating defkeymap.c_shipped
with loadkeys (kbd-1.08 recompiled with include/linux/keyboard.h
that comes with 2.6 kernel), things started work again.
Is there a reason not to include the above "keycode 183" line in
the shipped source (both defkeymap.map and defkeymap.c_shipped)?
The 2.6 kernel without it can be seem as a feature degradation
from 2.4 for 86/106 keyboard users, and I would like to know if
there is a case where having that line hurts. Is "keycode 183"
generated for completely different characters on other national
keyboards, and having that line is a feature degradation for
users of such keyboards? I have access to only 101, 86, and 106
keyboards so I cannot test this myself. Or maybe there are
other reasons to leave the default keymap as minimal as it
currently is in 2.6 tree?
prev parent reply other threads:[~2003-07-20 20:38 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
2003-07-20 20:53 ` junkio [this message]
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=7vhe5grkcr.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=aebr@win.tue.nl \
--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).