Re: [GIT PULL] iBFT features for v2.6.36

[Peter Jones <pjones@redhat.com>]

On 08/02/2010 10:29 PM, H. Peter Anvin wrote:
> On 08/02/2010 06:08 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Can you point me what 'standard ACPI mechanism' is? Like sticking
>> the code in the drivers/acpi ? And then having a generic driver to
>> handle the [i,a,s,m]BFT tables and maybe some subordinate ones for
>> specific pieces where the generic can't handle it?
>>
> 
> With the standard ACPI mechanism I meant RDSP -> {RSDT,XSDT} -> table.
> If it was easily possible to add SSDTs to this table structure then
> probably the best thing would have been to make them PnP devices.

The current iBFT specification and the current code (this push) includes the
ability to specify the location of the iBFT table using the standard ACPI table
mechanism, which is required on UEFI machines supporting iBFT, and which I
would encourage non-UEFI machines to also use where possible.  Obviously some
systems, especially BIOS-based machines doing iSCSI boot on expansion cards,
have difficulty with this, so we're not planning on de-supporting the old
memory scanning method.

-- 
        Peter

Obviously, a major malfunction has occurred.
		-- Steve Nesbitt, voice of Mission Control, January 28, 1986

01234567890123456789012345678901234567890123456789012345678901234567890123456789