From: Vojtech Pavlik <vojtech@suse.cz>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6 input drivers FAQ
Date: Sun, 1 Feb 2004 14:50:01 +0100 [thread overview]
Message-ID: <20040201135001.GA1804@ucw.cz> (raw)
In-Reply-To: <20040201141516.A28045@pclin040.win.tue.nl>
On Sun, Feb 01, 2004 at 02:15:16PM +0100, Andries Brouwer wrote:
> On Sun, Feb 01, 2004 at 11:06:44AM +0100, Vojtech Pavlik wrote:
>
> > Common problems and solutions with 2.6 input drivers:
>
> Good!
>
> > Get a recent version of kbd-utils, and recompile on a 2.6 kernel.
>
> Is there something called kbd-utils?
> I maintain the kbd package. Maybe recent versions will work
> on both 2.4 and 2.6, regardless where they were compiled.
>
> (Send bug reports to aeb@cwi.nl)
Sorry. I was typing that from memory. I'll fix it. Btw, could you make
the kbd package accept scancodes in the 0x80-0xff range (same as e000 to
e07f), if it is not yet there? And how about scancodes in the
0x100-0x1ff range? Will those work?
One more question: Will kbdrate work properly (use ioctls) when compiled
on a 2.6 kernels?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-02-01 13:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 10:06 2.6 input drivers FAQ Vojtech Pavlik
2004-02-01 13:15 ` Andries Brouwer
2004-02-01 13:50 ` Vojtech Pavlik [this message]
2004-02-01 15:14 ` Andries Brouwer
2004-02-02 9:35 ` Vojtech Pavlik
2004-02-02 9:43 ` Vojtech Pavlik
2004-02-01 13:51 ` Marcel J.E. Mol
2004-02-01 15:18 ` Andries Brouwer
2004-02-01 15:25 ` Andreas Jellinghaus
2004-02-01 15:56 ` Peter Osterlund
2004-02-01 16:58 ` Andreas Jellinghaus
2004-02-01 21:54 ` Vojtech Pavlik
2004-02-01 16:31 ` Joshua Kwan
2004-02-01 18:23 ` Gene Heskett
2004-02-02 16:45 ` Valdis.Kletnieks
2004-02-02 5:27 ` Valdis.Kletnieks
2004-02-02 9:23 ` Vojtech Pavlik
2004-02-02 18:12 ` Valdis.Kletnieks
2004-02-02 20:18 ` Vojtech Pavlik
2004-02-02 20:24 ` Joshua Kwan
2004-02-02 21:16 ` Vojtech Pavlik
2004-02-02 20:28 ` Valdis.Kletnieks
2004-02-02 21:19 ` Vojtech Pavlik
2004-02-02 9:24 ` Vojtech Pavlik
2004-02-02 9:29 ` Joshua Kwan
2004-02-01 21:54 ` 2.6 input drivers FAQ (ir-kbd-gpio.ko) Jose Luis Domingo Lopez
2004-02-02 10:27 ` Gerd Knorr
2004-02-16 22:42 ` Pavel Machek
2004-02-16 23:36 ` Arkadiusz Miskiewicz
2004-02-17 9:33 ` Gerd Knorr
2004-02-02 17:50 ` 2.6 input drivers FAQ Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2004-02-02 11:34 Andries.Brouwer
2004-02-02 12:25 ` Vojtech Pavlik
2004-02-02 12:44 Andries.Brouwer
2004-02-02 12:56 ` 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=20040201135001.GA1804@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox