Messages in this thread | | | Date | Sun, 1 Feb 2004 14:50:01 +0100 | From | Vojtech Pavlik <> | Subject | Re: 2.6 input drivers FAQ |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |