linux-kernel - Re: [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090623183153.GB12814@srcf.ucam.org>
Date:	Tue, 23 Jun 2009 19:31:53 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Len Brown <lenb@...nel.org>
Cc:	sfi-devel@...plefirmware.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial
	support

There seems to be a huge amount of overlap between SFI and ACPI. 
Couldn't this have simply taken the form of some additional ACPI tables 
and a decoupling of ACPI enumeration from runtime AML interpretation? 
How final is this spec?

I realise that we're pretty much constrained to implementing this if 
hardware actually ships with it, but it seems to be an additional 
firmware interface with no real benefit - as far as I can tell it's not 
possible for a platform to meaningfully implement both ACPI and SFI 
without duplicating information?

-- 
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/