Re: KDSETKEYCODE work with new input layer?
Skip Ford (skip.ford@verizon.net)
Tue, 1 Oct 2002 14:11:53 -0400
Vojtech Pavlik wrote:
> On Tue, Oct 01, 2002 at 01:41:27PM -0400, Skip Ford wrote:
> > Vojtech Pavlik wrote:
> > > On Tue, Oct 01, 2002 at 12:49:08PM -0400, Skip Ford wrote:
> > > >
> > > > The new AT driver
> > > > doesn't log any 'unknown scancode' messages for the same buttons the
> > > > old XT driver did.
> > >
> > > That means it understands them. If it did not, showkey -s wouldn't work.
> > >
> > > Just update the keymap - you don't need to change the scancode table if
> > > the keys are working.
> >
> > How do I make use of these keycodes in a map file?
> >
> > 0 press
> > 1 release
> > 14 release
> >
> > 0 press
> > 1 release
> > 15 release
>
> 0,1,14 is keycode 142 (Sleep) and 0,1,15 is keycode 143 (WakeUp),
> encoded because medium raw mode cannot handle keycodes above 128. If
> loadkeys doesn't allow keycodes 142 and 143, well, I'll have to fix it.
You'll have to fix it. I tried those before I asked. Actually I tried
141 and 142 but I was close. loadkeys rejects anything >= NR_KEYS (128)
All of my keys are recognized so I don't need any setkeycodes
functionality at all. I can probably get loadkeys to load my map so I
should be ok now. I was making things a lot harder than they had to be.
--
Skip
-
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/