[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F15B1EA.4060405@zytor.com>
Date: Tue, 17 Jan 2012 09:37:46 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: Len Brown <lenb@...nel.org>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Konrad Rzeszutek Wilk <konrad@...nel.org>,
"Brown, Len" <len.brown@...el.com>, linux-acpi@...r.kernel.org,
sfr@...b.auug.org.au, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, pjones@...hat.com
Subject: Re: Re-add ibft tree to linux-next please
On 01/17/2012 08:49 AM, Konrad Rzeszutek Wilk wrote:
>>
>> Are there really hardware/firmware configurations that support IBFT
>> and do not support ACPI?
>
> gPXE can be used in legacy environments. And it (gPXE) does not update
> the ACPI tables.
>
That's irrelevant. THe point is that iBFT *is* an ACPI table.
> I think that would work. And also if 'acpi_disabled=0' as you might
> have an IBFT table in memory that is _not_ hooked up to the ACPI tables.
That is *always* the case, the "finder" is nonstandard (because the ACPI
tables are largely non-extensible, says the one who has tried to
actually extend ACPI tables in memory.)
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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