From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753939Ab0BBCJ7 (ORCPT ); Mon, 1 Feb 2010 21:09:59 -0500 Received: from buzzloop.caiaq.de ([212.112.241.133]:34438 "EHLO buzzloop.caiaq.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753191Ab0BBCJ5 (ORCPT ); Mon, 1 Feb 2010 21:09:57 -0500 Date: Tue, 2 Feb 2010 03:09:38 +0100 From: Daniel Mack To: Zhang Rui Cc: "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "acpi4asus-user@lists.sourceforge.net" Subject: Re: ACPI device for ASUS EEEPC 1101HA not added Message-ID: <20100202020938.GH9007@buzzloop.caiaq.de> References: <20100201032554.GZ28972@buzzloop.caiaq.de> <1265073562.10648.12.camel@rzhang1-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1265073562.10648.12.camel@rzhang1-desktop> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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