| 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
| ||
|
Message-Id: <20060901125648.11883533.kamezawa.hiroyu@jp.fujitsu.com> Date: Fri, 1 Sep 2006 12:56:48 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: "Bjorn Helgaas" <bjorn.helgaas@...com> Cc: kmannth@...ibm.com, bjorn.helgaas@...com, lenb@...nel.org, robert.moore@...el.com, shaohua.li@...el.com, malattia@...ux.it, akpm@...l.org, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: one more ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [Re: 2.6.18-rc4-mm3] On Thu, 31 Aug 2006 21:15:55 -0600 (MDT) "Bjorn Helgaas" <bjorn.helgaas@...com> wrote: > Ok, this is starting to make sense. It sounds like your memory > device has _HID of PNP0C80 and _CID of PNP0C01 (or PNP0C02). > > The current ACPI driver binding algorithm in acpi_bus_find_driver() > looks at each driver, checking whether it can match either the _HID > or the _CID of a device. Since we try the motherboard driver first, > it matches the memory device _CID. > > I couldn't find a specific reference in the spec, but this seems > intuitively sub-optimal. It seems like it'd be better to look > first for a driver that can claim the _HID (which is more specific), > and only fall back to checking the _CIDs if no _HID-specific driver > is found. > I like it :) -Kame - 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