All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: andrej.gelenberg@udo.edu
Cc: linux-acpi@vger.kernel.org, acpi4asus-user@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Acpi4asus-user] ACPI device for ASUS EEEPC 1101HA not added
Date: Mon, 1 Feb 2010 13:51:55 +0100	[thread overview]
Message-ID: <20100201125155.GB28972@buzzloop.caiaq.de> (raw)
In-Reply-To: <cone.1265022400.369355.2380.1000@eeekiste>

On Mon, Feb 01, 2010 at 12:06:40PM +0100, andrej.gelenberg@udo.edu wrote:
> you need to whitelist your eee pc for OSI(Linux) in drivers/acpi/blacklist.c
> like this:
> 
> +        /*
> +        * On newer Eeepc, the interface used by eeepc-laptop (ASUS010)
> +        * is disabled without _OSI(Linux)
> +        */
> +       {
> +       .callback = dmi_enable_osi_linux,
> +       .ident = "Asus Eeepc-1101HA",
> +       .matches = {
> +                    DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer INC."),
> +                    DMI_MATCH(DMI_PRODUCT_NAME, "1101HA"),
> +               },
> +       },

Great, thanks. That worked. Is that already queued anywhere or do you
want me to send a proper patch?

Daniel


> Daniel Mack writes:
> 
> >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?
> >
> >
> >Thanks,
> >Daniel
> >

  reply	other threads:[~2010-02-01 12:52 UTC|newest]

Thread overview: 15+ 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 ` andrej.gelenberg-KJIyc1CJxjQ
2010-02-01 11:06   ` [Acpi4asus-user] " andrej.gelenberg
2010-02-01 12:51   ` Daniel Mack [this message]
2010-02-01 15:55     ` andrej.gelenberg-KJIyc1CJxjQ
2010-02-01 15:55       ` [Acpi4asus-user] " andrej.gelenberg
2010-02-02  6:02   ` Len Brown
2010-02-02  7:22     ` Corentin Chary
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
2010-02-02  2:17     ` Zhang, Rui
2010-02-02  2:31       ` Daniel Mack
2010-03-01 17:49         ` Len Brown

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=20100201125155.GB28972@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=andrej.gelenberg@udo.edu \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.