From: "Éric Piel" <Eric.Piel@tremplin-utc.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
mitr@volny.cz, otauber@web.de, linux-kernel@vger.kernel.org,
linux-input <linux-input@atrey.karlin.mff.cuni.cz>
Subject: Re: [PATCH 0/2] wistron_btns: More keymaps
Date: Tue, 20 Mar 2007 01:06:35 +0100 [thread overview]
Message-ID: <45FF258B.5090007@tremplin-utc.net> (raw)
In-Reply-To: <d120d5000703191428t11f2df22w5f28d49d2ecfcd52@mail.gmail.com>
19.03.2007 22:28, Dmitry Torokhov wrote/a écrit:
> On 3/15/07, Éric Piel <Eric.Piel@tremplin-utc.net> wrote:
>>
>> Ok, so let me summarize:
>>
>> There are two kinds of keys on those laptops (for which we are not sure
>> about the keycode that it should generate):
>> * Laptop screen on/off
>> * Display output selection (for instance: laptop/external/both)
>>
>> The possible keycodes that we could assign to them:
>> KEY_SCREEN
>> KEY_MEDIA
>> KEY_MODE
>> KEY_VIDEO
>> KEY_SWITCHVIDEOMODE
>> KEY_COMPUTER
>> KEY_PC
>>
>> From the discussion, I had the feeling this association would be the
>> less incorrect:
>> Screen on/off : KEY_SCREEN
>
> It looks like DVB folks chose to ise KEY_SCREEN and KEY_WINDOW to
> switch applications between full screen and windowed modes
Just for info, I couldn't find any reference to KEY_WINDOW. Anyway,
indeed, KEY_SCREEN is already used for "full screen" (although sometimes
it's KEY_ZOOM :-/) so better not using it if something else is possible.
> so we'll
> have to invent our own keycode. KEY_DISPLAYTOGGLE anyone?
What about KEY_DISPLAYONOFF ? :-)
What should be its value? Would 239 be fine?
>> Display selection : KEY_SWITCHVIDEOMODE
> I agree here.
BTW, I'm thinking of implementing led support. However, there are two
mechanisms for leds in the kernel: the "input layer" leds and the "full
feature" leds. The laptops may have up to three leds: mail, wifi,
bluetooth. The input layer has LED_MAIL but no wifi nor bluetooth. The
led subsystem has the advantage of the very extensible "trigger"
mechanism. Which of the subsystems would you recommend me to use?
See you,
Eric
next prev parent reply other threads:[~2007-03-20 0:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 23:05 [PATCH] Wistron button support for TravelMate 610 Eric Piel
2007-03-06 13:36 ` Dmitry Torokhov
2007-03-06 15:26 ` Éric Piel
2007-03-13 23:01 ` [PATCH 0/2] wistron_btns: More keymaps Eric Piel
2007-03-14 13:54 ` Dmitry Torokhov
2007-03-14 15:20 ` Éric Piel
2007-03-14 15:44 ` Dmitry Torokhov
2007-03-14 18:25 ` Vojtech Pavlik
2007-03-14 18:58 ` Dmitry Torokhov
2007-03-14 19:02 ` Dmitry Torokhov
2007-03-14 19:12 ` Éric Piel
2007-03-14 19:02 ` Vojtech Pavlik
2007-03-15 10:26 ` Éric Piel
2007-03-18 21:10 ` [PATCH 0/3] wistron_btns: More keymaps, take 2 Éric Piel
2007-03-27 3:39 ` Dmitry Torokhov
2007-03-18 21:10 ` [PATCH 1/3] wriston_btns: Add acerhk laptop database Éric Piel
2007-03-18 21:10 ` [PATCH 2/3] wistron_btns: Generic keymap Éric Piel
2007-03-18 21:10 ` [PATCH 3/3] wistron_btns: Declare keymaps as initdata Éric Piel
2007-03-19 21:28 ` [PATCH 0/2] wistron_btns: More keymaps Dmitry Torokhov
2007-03-20 0:06 ` Éric Piel [this message]
2007-03-13 23:05 ` [PATCH 1/2] wriston_btns: Add acerhk laptop database Eric Piel
2007-03-13 23:07 ` [PATCH 2/2] wistron_btns: Generic keymap Eric Piel
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=45FF258B.5090007@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mitr@volny.cz \
--cc=otauber@web.de \
--cc=vojtech@suse.cz \
/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