From: Vojtech Pavlik <vojtech@suse.cz>
To: Skip Ford <skip.ford@verizon.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: KDSETKEYCODE work with new input layer?
Date: Tue, 1 Oct 2002 22:53:25 +0200 [thread overview]
Message-ID: <20021001225325.C15796@ucw.cz> (raw)
In-Reply-To: <200210012004.g91K4SC7000390@pool-141-150-241-241.delv.east.verizon.net>; from skip.ford@verizon.net on Tue, Oct 01, 2002 at 04:04:27PM -0400
On Tue, Oct 01, 2002 at 04:04:27PM -0400, Skip Ford wrote:
> Vojtech Pavlik wrote:
> >
> > Well, if you get loadkeys to load the high keycodes, then indeed
> > everything is fine.
>
> Disregard my other email. I can get it to work if I redefine NR_KEYS in
> keyboard.h then rebuild the kernel and loadkeys using the new value.
>
> My map with extended keycodes loads and all the multimedia keys work
> without using setkeycodes. Have I done something horrible by upping
> NR_KEYS?
I don't think so it should be fine - actually NR_KEYS should be the same
as KEY_MAX in input.h probably.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2002-10-01 20:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 14:40 KDSETKEYCODE work with new input layer? Skip Ford
2002-10-01 9:54 ` Vojtech Pavlik
2002-10-01 12:31 ` Skip Ford
2002-10-01 13:17 ` Vojtech Pavlik
2002-10-01 15:32 ` Skip Ford
2002-10-01 15:41 ` Vojtech Pavlik
2002-10-01 15:54 ` Andries Brouwer
2002-10-01 15:55 ` Vojtech Pavlik
2002-10-01 16:29 ` Andries Brouwer
2002-10-07 12:06 ` Vojtech Pavlik
2002-10-07 12:52 ` Andries Brouwer
2002-10-07 13:23 ` Skip Ford
2002-10-07 13:39 ` Vojtech Pavlik
2002-10-01 16:49 ` Skip Ford
2002-10-01 16:51 ` Vojtech Pavlik
2002-10-01 17:41 ` Skip Ford
2002-10-01 17:39 ` Vojtech Pavlik
2002-10-01 18:11 ` Skip Ford
2002-10-01 18:38 ` Vojtech Pavlik
2002-10-01 20:04 ` Skip Ford
2002-10-01 20:53 ` Vojtech Pavlik [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=20021001225325.C15796@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=skip.ford@verizon.net \
/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