From: Daniel Mack <daniel@caiaq.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"acpi4asus-user@lists.sourceforge.net"
<acpi4asus-user@lists.sourceforge.net>
Subject: Re: ACPI device for ASUS EEEPC 1101HA not added
Date: Tue, 2 Feb 2010 03:09:38 +0100 [thread overview]
Message-ID: <20100202020938.GH9007@buzzloop.caiaq.de> (raw)
In-Reply-To: <1265073562.10648.12.camel@rzhang1-desktop>
On Tue, Feb 02, 2010 at 09:19:22AM +0800, Zhang Rui wrote:
> On Mon, 2010-02-01 at 11:25 +0800, Daniel Mack wrote:
> > On my new 1101HA Eeepc, the special function keys do not work. This is
> > because the asus-laptop driver fails to match the ACPI device named
> > "ASUS010". However, acpidump tells me a device with that name does
> > actually exist - the (simplified) disassembly of the DSDT is below.
> >
> > It looks like the gigantic parser state machine fails to add that
> > device for whatever reason. Any ideas how to fix that?
> >
> eeepc is handled in eeepci-laptop driver.
>
> ~/src/linux-2.6$ grep ASUS010 drivers/platform/*/*
> drivers/platform/x86/eeepc-laptop.c:#define EEEPC_ACPI_HID "ASUS010"
Yes, that I know. The driver was just unable to match the device because
it was not detected by the ACPI core. Works now with the patch Andrej
sent. I would still like to make sure it's getting merged mainline
sooner or later.
Thanks,
Daniel
prev parent reply other threads:[~2010-02-02 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 3:25 ACPI device for ASUS EEEPC 1101HA not added Daniel Mack
2010-02-01 11:06 ` [Acpi4asus-user] " andrej.gelenberg
2010-02-01 12:51 ` Daniel Mack
2010-02-01 15:55 ` andrej.gelenberg
2010-02-02 6:02 ` Len Brown
2010-02-02 7:22 ` Corentin Chary
2010-02-02 15:12 ` Matthew Garrett
2010-02-02 1:19 ` Zhang Rui
2010-02-02 2:09 ` Daniel Mack [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=20100202020938.GH9007@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.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