linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@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:31:43 +0100	[thread overview]
Message-ID: <20100202023142.GI9007@buzzloop.caiaq.de> (raw)
In-Reply-To: <8B81FACE836F9248894A7844CC0BA814250B6A0EAF@shzsmsx501.ccr.corp.intel.com>

On Tue, Feb 02, 2010 at 10:17:17AM +0800, Zhang, Rui wrote:
> > On Tue, Feb 02, 2010 at 09:19:22AM +0800, Zhang Rui wrote:
> > > 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.
> >
> Oh, can you give a link to this patch please?

http://permalink.gmane.org/gmane.linux.acpi.acpi4asus.user/3781


  reply	other threads:[~2010-02-02  2:31 UTC|newest]

Thread overview: 12+ 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 12:51   ` [Acpi4asus-user] " Daniel Mack
2010-02-01 15:55     ` andrej.gelenberg-KJIyc1CJxjQ
2010-02-02  6:02   ` [Acpi4asus-user] " 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
2010-02-02  2:17     ` Zhang, Rui
2010-02-02  2:31       ` Daniel Mack [this message]
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=20100202023142.GI9007@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).