linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiangfu Liu <xiangfu.z@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Fn + [KEYS] question
Date: Wed, 16 Sep 2009 22:44:01 +0800	[thread overview]
Message-ID: <4AB0F9B1.90606@gmail.com> (raw)
In-Reply-To: <4AB0AEF6.7020103@gmail.com>

Xiangfu Liu wrote:
> Hi Dmitry
> 
>>>  thanks for the reply.
>>> see [1], I change the [Red arrow] key to [ALTGR] then I can easy change the 
>>> defkeymap.map. make all the red keys work.
>>>
>>> but for the [Blue Fn] key. I don't know how to make it work in keymap?
>>> there is [SHIFT] [CONTROL] [SHIFT] [ALTGR] four modifier keys.
>>> all used. so I can not may the [Fn] to those four modifier keys.
>>>
>>> can I make the leftAlt and rightAlt generate different keys?
>>> like:
>>>  LeftAlt + 'U' = Alt + 'U'
>>>  RightAlt + 'U' = '7'
>>>
>> Keyboard driver supports 9 modifiers total, you should be able use one
>> of these for your numeric buttons.
>>
> 
> oh. can you give me some tips on the other modifiers.
> how to define them? 
> can I just change the defkeymap.map file?
> or I must change the source code?
> 
Hi Dmitry I found this[1] in the 'man keymaps', three are 9 modifiers.
but the in defkaymap.map, there is alwasy like:

control keycode  53 = Delete

there is no ctrll in the defkeymap.map.
how to implement this?
ShiftL + u = U
ShiflR + u = 7

thansk for help


[1]
Which  of  the  actions bound to a given key is taken when it is pressed depends on what modifiers are in effect at
       that moment.  The keyboard driver supports 9 modifiers. These modifiers are labeled (completely arbitrarily) Shift,
       AltGr,  Control, Alt, ShiftL, ShiftR, CtrlL, CtrlR and CapsShift.  Each of these modifiers has an associated weight
       of power of two according to the following table:

              modifier                weight

              Shift                     1
              AltGr                     2
              Control                   4
              Alt                       8
              ShiftL                   16
              ShiftR                   32
              CtrlL                    64
              CtrlR                   128
              CapsShift               256



-- 
Xiangfu Liu
Email: xiangfu at qi-hardware dot com
Web: http://www.qi-hardware.com

  reply	other threads:[~2009-09-16 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  7:24 Fn + [KEYS] question Xiangfu Liu
2009-09-16  7:32 ` Dmitry Torokhov
2009-09-16  7:43   ` Xiangfu Liu
2009-09-16  8:06     ` Dmitry Torokhov
2009-09-16  9:25       ` Xiangfu Liu
2009-09-16 14:44         ` Xiangfu Liu [this message]
2009-09-16 16:33           ` Dmitry Torokhov
2009-09-16 17:24             ` Xiangfu Liu
2009-09-16 17:40               ` Dmitry Torokhov
2009-09-17  2:31                 ` Xiangfu Liu
2009-09-18  5:45                   ` Dmitry Torokhov
2009-09-18  6:45                     ` Xiangfu Liu
2009-09-18  6:49                       ` Dmitry Torokhov

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=4AB0F9B1.90606@gmail.com \
    --to=xiangfu.z@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).