From: Vojtech Pavlik <vojtech@suse.cz>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Skip Ford <skip.ford@verizon.net>,
linux-kernel@vger.kernel.org
Subject: Re: KDSETKEYCODE work with new input layer?
Date: Tue, 1 Oct 2002 17:55:37 +0200 [thread overview]
Message-ID: <20021001175537.A13220@ucw.cz> (raw)
In-Reply-To: <20021001155428.GA19122@win.tue.nl>; from aebr@win.tue.nl on Tue, Oct 01, 2002 at 05:54:28PM +0200
On Tue, Oct 01, 2002 at 05:54:28PM +0200, Andries Brouwer wrote:
> On Tue, Oct 01, 2002 at 05:41:29PM +0200, Vojtech Pavlik wrote:
>
> > > Will you be releasing an updated kbd package?
> >
> > Well, I'm not the maintainer of the kbd package, but I probably will
> > have to release a new tool to set the keycode table.
>
> If possible, make it as a patch of the old [gs]etkeycodes, and such
> that it recognizes the kernel version and does the right thing
> on both 2.4 and 2.6. This is a fairly obscure area, so the utility
> should be as self-documenting as possible.
Ok. Where is the most recent version of [gs]etkeycodes?
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-01 15:50 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 [this message]
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
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=20021001175537.A13220@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--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