| 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: <20090429212924.GA7900@srcf.ucam.org> Date: Wed, 29 Apr 2009 22:29:24 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Mario Limonciello <mario_limonciello@...l.com> Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/3] Add support for more dell-wmi hotkeys On Wed, Apr 29, 2009 at 04:24:47PM -0500, Mario Limonciello wrote: > I've obtained one of these and taken a look at it with a copy of Win 7 > and compared with dell-wmi and my patchset applied. This platform's WMI > support was introduced before Win7's WMI spec was drafted, and so it > doesn't adhere to the spec. I think the best thing to do will be create > a DMI table to match for keys that are only on a per system basis for > anything before this spec was ready. I don't expect many other > platforms like this, but it will allow for additional granularity in > case something in the future ever deviates spec as well. Ok. Is there any programmatic way to determine whether a given Dell complies with your WMI spec or not? I'd prefer not to use DMI tables unless it's the only way to identify the machines - the risk is that there'll be something else that also uses its own codes and will just behave oddly until someone figures out why it's broken. -- Matthew Garrett | mjg59@...f.ucam.org -- 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