Re: 2.6 input drivers FAQ

Vojtech Pavlik
2004-02-02T12:24:53Z

On Mon, Feb 02, 2004 at 12:34:00PM +0100, Andries.Brouwer@cwi.nl wrote:

> > Well, I think it's a bad idea to have the userspace tool know about the
> > e0 thing at all. It should be just opaque numbers to it.
>
> But how is the user to invent these opaque numbers?
> She uses showkey -s to see what scancodes a key produces,
> and then setkeycodes to assign a keycode to them.

That's another problem. showkey -s will show nothing if the keys don't
work in 2.6, and nothing useful for setkeycodes usage if they do.

I'm planning to add a new event type to report the raw scancodes through
the event interface, though I'm still yet not decided about how exactly
to do it and whether to use this to do real raw mode instead of the
simulated one where possible. I don't think the later is a good idea.

> > I don't have a problem with swapping the set3 table, if setkeycodes
> > works reasonably now for scancodes above 128.
>
> Above 128, yes. Above 256, no.
> The interface is a char - 8 bits only.

Even for scancodes? Well, in that case I'll have to keep the kludge as
it is. Or have setkeycodes use EVIOCSKEYCODE.

> (So, right now, NR_KEYS > 256 is not useful.)

--
Vojtech Pavlik
SuSE Labs, SuSE CR