All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:28:16 +0200	[thread overview]
Message-ID: <20040530212816.GA2987@ucw.cz> (raw)
In-Reply-To: <MPG.1b2467af841573119896ae@news.gmane.org>

On Sun, May 30, 2004 at 10:51:18PM +0200, Giuseppe Bilotta wrote:

> > Interesting. Nevertheless it's just a naming difference, and thus
> > shouldn't be a problem.
> 
> Well, it's not just that, not if we want Meta kernel keys to 
> become Meta X keys. Which wouldn't be a bad thing, since it 
> would mean we'd have the keyboard acting the same under console 
> and X. But in this case it would be nice if Linux knew about 
> more modifiers than just shift, ctrl, alt, meta.

Keep in mind that the kernel keys we're talking about are keycodes, not
keysyms, and thus are not a result of a keymap. On the other hand, the
xkb tables you've shown are for keysyms.

The equivalences are:

Kernel		   XKB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
KEY_LEFTALT    ==  key <LALT> 
KEY_RIGHTALT   ==  key <RALT> 
KEY_LEFTMETA   ==  key <LWIN> 
KEY_RIGHTMETA  ==  key <RWIN> 
KEY_COMPOSE    ==  key <MENU> 

There is a 1:1 mapping. 

Now, if you want to make them _do_ the same both in X and on console,
then we're talking keymaps, and there I think is no problem again,
because the kernel can handle up to 9 modifiers as far as I know,
although they don't all have names.

linux/keyboard.h:#define NR_SHIFT       9

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-05-30 21:27 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
2004-05-30 20:51                       ` Giuseppe Bilotta
2004-05-30 21:28                         ` Vojtech Pavlik [this message]
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=20040530212816.GA2987@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.