| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 2 Feb 2010 03:09:38 +0100 From: Daniel Mack <daniel@...aq.de> To: Zhang Rui <rui.zhang@...el.com> Cc: "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "acpi4asus-user@...ts.sourceforge.net" <acpi4asus-user@...ts.sourceforge.net> Subject: Re: ACPI device for ASUS EEEPC 1101HA not added 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists