mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Rzeszutek <konrad@darnok.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Doug Maxey <dwm@enoyolf.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, greg@kroah.com, darnok@68k.org,
	pjones@redhat.com, konradr@redhat.com,
	konradr@linux.vnet.ibm.com, randy.dunlap@oracle.com,
	lenb@kernel.org, mike.anderson@us.ibm.com, dwm@austin.ibm.com,
	arjan@infradead.org, michaelc@cs.wisc.edu,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH] Add iSCSI iBFT support (v0.4.5)
Date: Mon, 28 Jan 2008 15:46:58 -0500	[thread overview]
Message-ID: <200801281547.00865.konrad@darnok.org> (raw)
In-Reply-To: <479E2E89.7030704@zytor.com>

> iBFT is not platform-independent; it only makes sense on platforms with
> ACPI (and even then, just barely; ACPI is a poor fit for it and it was
> probably "integrated" with ACPI for political reasons.)

The spec just mentions that iBFT table has to be "compatible with an ACPI 
table format" and nothing else. In reality I've only tested this on x86_64 
and i386. We can limit it to be X86 || IA64 but I wouldn't make it dependent 
on ACPI - as this data does not necessarily have to be exported via ACPI.

  reply	other threads:[~2008-01-28 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 22:06 Konrad Rzeszutek
2008-01-27  6:01 ` Andrew Morton
2008-01-27  6:01 ` Andrew Morton
2008-01-27 16:47   ` Randy Dunlap
2008-01-28 11:27   ` Andy Whitcroft
2008-01-28 19:04   ` Konrad Rzeszutek
2008-01-28 19:11     ` Doug Maxey
2008-01-28 19:35       ` H. Peter Anvin
2008-01-28 20:46         ` Konrad Rzeszutek [this message]
2008-01-28 21:13           ` Peter Jones
2008-01-30 21:47             ` Konrad Rzeszutek
2008-01-29 19:13     ` Mike Christie
2008-01-29 19:44       ` Greg KH

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=200801281547.00865.konrad@darnok.org \
    --to=konrad@darnok.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=arjan@infradead.org \
    --cc=darnok@68k.org \
    --cc=dwm@austin.ibm.com \
    --cc=dwm@enoyolf.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=konradr@linux.vnet.ibm.com \
    --cc=konradr@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=mike.anderson@us.ibm.com \
    --cc=pjones@redhat.com \
    --cc=randy.dunlap@oracle.com \
    /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

Powered by JetHome