public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Crespel <fabien@crespel.net>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Timo Hoenig <thoenig@nouse.net>,
	Nicolas Trangez <ikke@nicolast.be>,
	sziwan@users.sourceforge.net, linux-acpi@vger.kernel.org,
	Daniel Nascimento <dnascimento@gmail.com>,
	acpi4asus-user@lists.sourceforge.net
Subject: Re: Fwd: [PATCH 01/02] Initial work to let ACPI buttons work over INPUT layer
Date: Thu, 15 Jan 2009 13:31:47 +0100	[thread overview]
Message-ID: <496F2CB3.5000102@crespel.net> (raw)
In-Reply-To: <71cd59b00901140157n760b8e55i13119bfdb193b9d@mail.gmail.com>

Corentin Chary wrote:
> Hi,
> Just done a patch based on eeepc-laptop.
> You can get it there:
> http://git.iksaif.net/?p=acpi4asus.git;a=shortlog;h=refs/heads/asus-laptop-input
> I didn't test it yet, I'll only have my laptops this weekend.
> Could you test it please ?
> Thanks
> 

Hello,

I haven't tested this patch, but there is a mistake in the keymap here:

{KE_KEY, 0x7D, KEY_BLUETOOTH}, /* Bluetooth up */
{KE_KEY, 0x7E, KEY_BLUETOOTH}, /* Bluetooth down */

These are not keys, they are notifications that occur *after* the bluetooth state
is changed by the firmware (by pressing the bluetooth key on some models, for
example). Therefore, they should not be reported to the input layer.

There is also a 0x88 scancode for the radio key on some models. On Windows, this
key cycles through radio states: WLAN + BT => WLAN => BT => None. AFAIK there is
no equivalent on Linux yet for such a key... What would be best to do to support it?

- Fabien.


      parent reply	other threads:[~2009-01-15 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 20:34 [PATCH 01/02] Initial work to let ACPI buttons work over INPUT layer Daniel Oliveira Nascimento
2008-12-10  9:26 ` Timo Hoenig
2008-12-10 10:31   ` Corentin Chary
2008-12-10 10:45     ` Timo Hoenig
2008-12-19 16:34 ` Fwd: " Daniel Nascimento
2009-01-07 11:38   ` Timo Hoenig
2009-01-12 11:59     ` Corentin Chary
2009-01-12 12:00       ` Corentin Chary
2009-01-14  9:57         ` Corentin Chary
2009-01-14 12:05           ` Daniel Nascimento
2009-01-15 12:31           ` Fabien Crespel [this message]

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=496F2CB3.5000102@crespel.net \
    --to=fabien@crespel.net \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentin.chary@gmail.com \
    --cc=dnascimento@gmail.com \
    --cc=ikke@nicolast.be \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sziwan@users.sourceforge.net \
    --cc=thoenig@nouse.net \
    /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