public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter Jones <pjones@redhat.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	Konrad Rzeszutek <konrad@hera.kernel.org>,
	torvalds@linux-foundation.org, James.Bottomley@suse.de,
	linux-kernel@vger.kernel.org, lenb@kernel.org,
	michaelc@cs.wisc.edu, mcb30@ipxe.org
Subject: Re: [GIT PULL] iBFT features for v2.6.36
Date: Tue, 03 Aug 2010 16:23:19 -0700	[thread overview]
Message-ID: <4C58A4E7.4030800@zytor.com> (raw)
In-Reply-To: <4C582918.5080602@redhat.com>

On 08/03/2010 07:35 AM, Peter Jones wrote:
> 
> 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.
> 

Not just expansion cards, but also post-INT19 software solutions.

	-hpa

  reply	other threads:[~2010-08-03 23:24 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
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 [this message]
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=4C58A4E7.4030800@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=mcb30@ipxe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox