From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Len Brown <lenb@kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"H. Peter Anvin" <hpa@zytor.com>,
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 11:49:20 -0500 [thread overview]
Message-ID: <20120117164920.GA5111@phenom.dumpdata.com> (raw)
In-Reply-To: <4F1580DE.1060002@kernel.org>
On Tue, Jan 17, 2012 at 09:08:30AM -0500, Len Brown wrote:
>
> > The trick is that we also have to retain the code functionality if
> > "# CONFIG_ACPI is not set" to scan the memory for the iBFT. That part
> > should definitly _not_ be moved to drivers/acpi. It could be moved to
> > arch/x86/ .. but it could also stay in drivers/firmware. <shrugs>
>
>
> 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.
>
> If yes, do they require an OS that has CONFIG_ACPI=n?
I can't think of anybody nowadays doing CONFIG_ACPI=n for x86.
Is there anybody doing it?
> Or would finding the table with CONFIG_ACPI=y and acpi_disabled=1
> be sufficient?
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.
next prev parent reply other threads:[~2012-01-17 16:52 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 [this message]
2012-01-17 17:37 ` H. Peter Anvin
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=20120117164920.GA5111@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.