From: Vojtech Pavlik <vojtech@suse.cz>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: Re: keyboard problem with 2.6.6
Date: Sun, 30 May 2004 22:31:46 +0200 [thread overview]
Message-ID: <20040530203146.GA1941@ucw.cz> (raw)
In-Reply-To: <MPG.1b2424ed871e68c89896aa@news.gmane.org>
On Sun, May 30, 2004 at 06:08:39PM +0200, Giuseppe Bilotta wrote:
> > The Linux kernel reports them as KEY_LEFTMETA, KEY_RIGHTMETA and
> > KEY_COMPOSE.
>
> In X standard keyboards Meta is mapped as the second symbol for
> Alt.
>
> // definition for the extra keys on 104-key "Windows95" keyboards
> xkb_symbols "pc104" {
> include "us(generic101)"
> key <LALT> { [ Alt_L, Meta_L ] };
> key <RALT> { [ Alt_R, Meta_R ] };
> key <LWIN> { [ Super_L ] };
> key <RWIN> { [ Super_R ] };
> key <MENU> { [ Menu ] };
>
> // modifier mappings
> modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
> modifier_map Mod4 { Super_L, Super_R };
> };
>
> // definition of Euro-style, Right "logo" key == [Mode_switch, Multi_key]
> xkb_symbols "pc104euro" {
> include "us(pc104)"
> key <RALT> { [ Mode_switch ]
> };
> key <RWIN> { [ Multi_key ] };
> };
Interesting. Nevertheless it's just a naming difference, and thus
shouldn't be a problem.
> > I'm not very familiar with xkb configuration. Perhaps you'd be willing
> > to write that definition file? I'll certainly help you from the kernel
> > side - I can even generate a list of keycode - scancode - meaning
> > relations for you.
>
> If you do generate a list of keycode - scancode - meaning pairs
> it will surely make my life easier.
>
> I'm not particularly familiar with xkb configuration either. I
> can *probably* make it work (i.e. test it as functional) on my
> Dell Inspiron 8200 keyboard and on a standard pc104 keyboard
> only. You probably need somebody else to work out the details
> for other keyboards, though.
Ok, I'll try to produce something.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-05-30 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040528154307.142b7abf.akpm@osdl.org>
2004-05-29 7:09 ` Fw: Re: keyboard problem with 2.6.6 Vojtech Pavlik
2004-05-29 13:14 ` Giuseppe Bilotta
2004-05-29 13:37 ` Vojtech Pavlik
2004-05-29 15:12 ` Giuseppe Bilotta
2004-05-29 15:44 ` Vojtech Pavlik
2004-05-29 17:18 ` Dmitry Torokhov
2004-05-29 18:23 ` Vojtech Pavlik
2004-05-30 10:20 ` Giuseppe Bilotta
2004-05-30 11:43 ` Vojtech Pavlik
2004-05-30 12:38 ` Giuseppe Bilotta
2004-05-30 12:59 ` Vojtech Pavlik
2004-05-30 16:08 ` Giuseppe Bilotta
2004-05-30 20:31 ` Vojtech Pavlik [this message]
2004-05-30 20:51 ` Giuseppe Bilotta
2004-05-30 21:28 ` Vojtech Pavlik
2004-05-31 12:43 ` Giuseppe Bilotta
2004-05-30 23:21 ` keyboard: kernel and X Andries Brouwer
2004-05-31 12:43 ` Giuseppe Bilotta
2004-06-01 11:22 ` Fw: Re: keyboard problem with 2.6.6 Vojtech Pavlik
2004-05-29 22:40 ` Dmitry Torokhov
2004-05-29 14:07 ` Andries Brouwer
2004-05-29 14:18 ` 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=20040530203146.GA1941@ucw.cz \
--to=vojtech@suse.cz \
--cc=bilotta78@hotpop.com \
--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