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: Mon, 1 Feb 2010 13:51:55 +0100 From: Daniel Mack <daniel@...aq.de> To: andrej.gelenberg@....edu Cc: linux-acpi@...r.kernel.org, acpi4asus-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [Acpi4asus-user] ACPI device for ASUS EEEPC 1101HA not added On Mon, Feb 01, 2010 at 12:06:40PM +0100, andrej.gelenberg@....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 > > -- 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