From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Len Brown <lenb@kernel.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
"Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
pjones@redhat.com
Subject: Re: Re-add ibft tree to linux-next please
Date: Tue, 17 Jan 2012 09:37:46 -0800 [thread overview]
Message-ID: <4F15B1EA.4060405@zytor.com> (raw)
In-Reply-To: <20120117164920.GA5111@phenom.dumpdata.com>
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.
prev parent reply other threads:[~2012-01-17 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:53 Re-add ibft tree to linux-next please Konrad Rzeszutek Wilk
2011-12-12 22:44 ` Stephen Rothwell
2011-12-12 23:10 ` Konrad Rzeszutek Wilk
2011-12-12 23:25 ` H. Peter Anvin
2011-12-13 2:15 ` Konrad Rzeszutek Wilk
2012-01-17 14:08 ` Len Brown
2012-01-17 16:49 ` Konrad Rzeszutek Wilk
2012-01-17 17:37 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F15B1EA.4060405@zytor.com \
--to=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=konrad@kernel.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).