From: Vojtech Pavlik <vojtech@suse.cz>
To: "P. Christeas" <p_christ@hol.gr>
Cc: lkml <linux-kernel@vger.kernel.org>, omnibook@zurich.csail.mit.edu
Subject: Re: Solved: atkbd w 2.6.2rc1 : HowTo for extra (inet) keys ?
Date: Sat, 24 Jan 2004 09:39:58 +0100 [thread overview]
Message-ID: <20040124083958.GA445@ucw.cz> (raw)
In-Reply-To: <200401240428.30493.p_christ@hol.gr>
On Sat, Jan 24, 2004 at 04:28:30AM +0200, P. Christeas wrote:
> After spending my evening on it :-( I managed to find the correct keys for
> the Omnibook XE3:
> (I could only reverse-engineer the previous hack I 've had for it)
> Download and hack the 'console-tools' package (from sourceforge, project
> "lct") so that 'setkeycodes' does accept keycodes >127.
>
> Vojtech, is 512 the upper bound for <keycode> at setkeycodes?
>
> Using 2.6.2-rc1, issue:
> setkeycodes e071 236
> setkeycodes e072 237
> setkeycodes e073 238
> setkeycodes e074 239
>
> so that the upper (near the screen) row of "internet" buttons is assigned to
> the keys X expect to receive.
> e071 etc. can be found using 'showkey -s'
> I still don't get where 236 came from (so that I could help other kbds, as
> well).
The almost right solution here would be to write an xkb keyboard
description that matches the 2.6 keycode->scancode mappings, so that
once you get the 'setkeycodes' command right, both the kernel and X will
understand the keys correctly.
With your approach you got the keys correct solely in X, not the kernel.
I'll take a look at this.
The completely right approach would be to teach X to either use the
event interface or at least the medium raw mode.
> > On Fri, Jan 23, 2004 at 10:04:27PM +0200, P. Christeas wrote:
> > > Hello again.
> > > I just reverted my atkbd.c code to your version (Linus's tree) and
> > > unfortunately have 4 keys 'missing' from my HP Omnibook XE3GC extra
> > > "internet keys".
> > > Question 1: Can I fix the table from userland, using some utility? That
> > > is, can I upload an updated table into the kernel, so that I don't have
> > > to reboot?
> >
> > 'setkeycodes' can do that.
> >
> > > Q 2: Do you have any HowTo/QA for that?
> >
> > Not yet, but I'll have to write one.
> >
> > > Q 3: Will that work under X? (which AFAIK reads the 'raw' codes)
> >
> > X needs to be set up as well. In 2.6, X doesn't get real raw codes but
> > instead simulated raw codes generated by the kernel.
> >
> > > Q 4: It has been rather difficult for me to compute the scancodes needed
> > > for the table. Could you put the "formula" onto the HowTo?
> > >
> > > FYI, the codes are:
> > > "www": Unknown key pressed (translated set 2, code 0xf3 on
> > > isa0060/serio0). "Mail": Unknown key pressed (translated set 2, code
> > > 0xf4 on isa0060/serio0). "Launch": Unknown key pressed (translated set 2,
> > > code 0xf2 on isa0060/serio0). "Help": Unknown key pressed (translated
> > > set 2, code 0xf1 on isa0060/serio0).
> >
> > The formula for setkeycodes is:
> >
> > if (code > 0x100)
> > you're out of luck, setkeycodes doesn't handle this yet;
> > else if (code > 0x80)
> > result = code - 0x80 + 0xe000;
> > else
> > result = code;
> >
> > And then you use 'setkeycodes result keycode',
> >
> > where keycode you find in include/linux/input.h.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-01-24 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 20:04 atkbd w 2.6.2rc1 : HowTo for extra (inet) keys ? P. Christeas
2004-01-23 21:09 ` Vojtech Pavlik
2004-01-24 2:28 ` Solved: " P. Christeas
2004-01-24 8:39 ` Vojtech Pavlik [this message]
2004-01-24 18:37 ` Andries Brouwer
2004-01-26 19:29 ` [OmniBook] " Nigel Cunningham
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=20040124083958.GA445@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=omnibook@zurich.csail.mit.edu \
--cc=p_christ@hol.gr \
/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