From: Ike Panhc <ike.pan@canonical.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>, Len Brown <len.brown@intel.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Corentin Chary <corentincj@iksaif.net>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@linux.intel.com>, Thomas Renninger <trenn@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ideapad-laptop: add new driver
Date: Fri, 13 Aug 2010 17:27:23 +0800 [thread overview]
Message-ID: <4C650FFB.7090602@canonical.com> (raw)
In-Reply-To: <1281690893.23680.475.camel@localhost>
On 08/13/2010 05:14 PM, David Woodhouse wrote:
>
> Hm, interesting. What model (and BIOS version) are you testing with?
I have two machine, B550 and S10-3, the BIOS date/version of S10-3 is the
same with you.
>
> On my S10-3, (DMI BIOS version 2ACN23WW, date 03/12/2010), I get these
> keys through the normal keyboard controller -- and we can tell the
> brightness up/down apart, too.
>
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=9cd075e3
>
> Do you see those keycodes too... and do they *stop* arriving through the
> keyboard controller when you load your driver?
>
Yes, IIRC EC will send i8042 keycode when you booting with QS button, not
with power button. atkbd.c reports unknown key after booting with QS button.
next prev parent reply other threads:[~2010-08-13 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 4:08 [PATCH] ideapad-laptop: add new driver Ike Panhc
2010-08-13 6:37 ` Corentin Chary
2010-08-13 6:53 ` Ike Panhc
2010-08-13 7:01 ` Corentin Chary
2010-08-13 7:15 ` Ike Panhc
2010-08-13 9:22 ` David Woodhouse
2010-08-13 9:14 ` David Woodhouse
2010-08-13 9:27 ` Ike Panhc [this message]
2010-08-13 9:34 ` David Woodhouse
2010-08-14 2:56 ` Ike Panhc
2010-08-14 9:49 ` David Woodhouse
2010-08-15 2:33 ` Len Brown
2010-08-15 8:14 ` Florian Echtler
2010-08-15 8:20 ` Florian Echtler
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=4C650FFB.7090602@canonical.com \
--to=ike.pan@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=corentincj@iksaif.net \
--cc=dwmw2@infradead.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=trenn@suse.de \
/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).