From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Konrad Rzeszutek <konrad@hera.kernel.org>,
torvalds@linux-foundation.org, James.Bottomley@suse.de,
linux-kernel@vger.kernel.org, pjones@redhat.com, lenb@kernel.org,
michaelc@cs.wisc.edu
Subject: Re: [GIT PULL] iBFT features for v2.6.36
Date: Mon, 02 Aug 2010 13:26:59 -0700 [thread overview]
Message-ID: <4C572A13.4010303@zytor.com> (raw)
In-Reply-To: <20100802195248.GB32503@andromeda.dapyr.net>
On 08/02/2010 12:52 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Unfortunately, we're increasingly seeing a proliferation of this kind of
>> nonstandard ACPI tables, because it is difficult to add data to ACPI at
>
> Keep in mind that iBFT is now a standard (woot!)
>
Yes, but the discovery method is ad hoc, as opposed to the standard ACPI
mechanisms.
>> runtime. gPXE creates an aBFT table for AoE and sBFT for SRP, and
>> memdisk uses mBFT for MEMDISK at the moment.
>
> Oh man, didn't know those existed at all.
>>
>> It would be good to have some kind of common structure framework for these.
>
> I need to grok those tables some more to figure out what they all do.
More or less the same thing as iBFT, but for AoE, SRP, or in-memory disk.
-hpa
next prev parent reply other threads:[~2010-08-02 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 14:36 [GIT PULL] iBFT features for v2.6.36 Konrad Rzeszutek
2010-08-02 18:22 ` H. Peter Anvin
2010-08-02 19:52 ` Konrad Rzeszutek Wilk
2010-08-02 20:26 ` H. Peter Anvin [this message]
2010-08-03 1:08 ` Konrad Rzeszutek Wilk
2010-08-03 2:29 ` H. Peter Anvin
2010-08-03 12:56 ` Konrad Rzeszutek Wilk
2010-08-03 14:35 ` Peter Jones
2010-08-03 23:23 ` H. Peter Anvin
2010-08-04 13:38 ` [GIT PULL] iBFT features for v2.6.36 .. Question about LinuxCon Konrad Rzeszutek Wilk
2010-08-04 13:47 ` James Bottomley
2010-08-04 15:39 ` Linus Torvalds
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=4C572A13.4010303@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@suse.de \
--cc=konrad@hera.kernel.org \
--cc=konrad@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pjones@redhat.com \
--cc=torvalds@linux-foundation.org \
/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.