| 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: <20110719132157.GG8006@one.firstfloor.org> Date: Tue, 19 Jul 2011 15:21:58 +0200 From: Andi Kleen <andi@...stfloor.org> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Andi Kleen <andi@...stfloor.org>, Prarit Bhargava <prarit@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 01/34] System Firmware Interface On Tue, Jul 19, 2011 at 10:05:44AM +0100, Alan Cox wrote: > > Could you expand somewhat WHY you want this. What is wrong with the > > current code? > > See the previous discussions Ok I will put that now as description into all my code submissions @) Seriously, that REALLY belongs into a patch description. > > > As for user space access on x86 "dmidecode"/libdmi works for nearly everyone, > > doesn't it? > > "on x86" (and on PC only generally) > > There are three core problems > > 1. DMI in this sense is basically an x86 PC class device hack > 2. It is obsoleted and at some point it'll vanish even on PC Huh? What obsoleted it? > 3. Every other platform without DMI would benefit from the > interface being generic Can you expand on that? The information will be always system specific anyways. Do you really think there's that much commonality? -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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