linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joey Lee <jlee@novell.com>
Cc: corentin.chary@gmail.com, Takashi Iwai <tiwai@novell.com>,
	Thomas Renninger <trenn@novell.com>,
	mjg59@srcf.ucam.org, carlos@strangeworlds.co.uk, jbenc@suse.cz,
	linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/3] Support enable Acer Launch Manager mode
Date: Mon, 18 Oct 2010 01:20:48 -0700	[thread overview]
Message-ID: <20101018082048.GC8655@core.coreip.homeip.net> (raw)
In-Reply-To: <4CBC6D61020000230002205F@novprvlin0050.provo.novell.com>

On Sun, Oct 17, 2010 at 10:53:05PM -0600, Joey Lee wrote:
> Hi Dmitry, 
> 
> 於 日,2010-10-17 於 21:07 -0700,Dmitry Torokhov 提到:
> > 
> > I believe that we simply need to tell EC to keep its hands off RF
> > switch. As long as key is properly reported through input layer rfkill
> > should be able to control the RF equipment, either via rfkill-input
> > in-kernel shortcut or userspace daemon (when it is ready).
> > 
> 
> I agree EC don't need touch the RF switch by default, I will contact
> with them to discuss.
> 
> But, 
> Currently, the Acer BIOS already shipped to world wide, and BIOS guys
> give me tThat's why I contribute launch-manager mode patch to here.
> 

I understand that certain BIOSes do, by default, toggle the switch. I
also believe that we want to disable this. The question that still is
not answered why we need the module option? Why don't we _always_
tell EC to keep its hands off RF switch?

Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-10-18  8:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  4:53 [PATCH 2/3] Support enable Acer Launch Manager mode Joey Lee
2010-10-18  8:20 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-30 16:28 Joey Lee
2010-10-21  3:35 Joey Lee
2010-10-19 13:25 Joey Lee
2010-10-19 13:28 ` Corentin Chary
2010-10-19 15:49   ` Dmitry Torokhov
2010-10-19 16:03     ` Corentin Chary
2010-10-19 16:49       ` Dmitry Torokhov
2010-10-19 11:15 Joey Lee
2010-10-19 13:07 ` Corentin Chary
2010-10-19  9:55 Joey Lee
2010-10-19 10:51 ` Corentin Chary
2010-10-19  8:09 Joey Lee
2010-10-19  2:48 Joey Lee
2010-10-18  2:32 Joey Lee
2010-10-18  4:07 ` Dmitry Torokhov
2010-10-18  7:19 ` Carlos Corbacho
2010-10-18  7:55   ` Corentin Chary
2010-10-18  8:14     ` Dmitry Torokhov
2010-10-18  8:40       ` Corentin Chary
2010-10-15  8:02 Joey Lee
2010-10-15 17:11 ` Carlos Corbacho
2010-10-13  3:47 [PATCH 1/3] Add acer wmi hotkey events support Lee, Chun-Yi
2010-10-13  3:47 ` [PATCH 2/3] Support enable Acer Launch Manager mode Lee, Chun-Yi
2010-10-13 18:26   ` 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=20101018082048.GC8655@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=corentin.chary@gmail.com \
    --cc=jbenc@suse.cz \
    --cc=jlee@novell.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tiwai@novell.com \
    --cc=trenn@novell.com \
    /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).