From: "H. Peter Anvin" <hpa@zytor.com>
To: Doug Maxey <dwm@enoyolf.org>
Cc: Konrad Rzeszutek <konrad@darnok.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 11:35:37 -0800 [thread overview]
Message-ID: <479E2E89.7030704@zytor.com> (raw)
In-Reply-To: <22101.1201547493@bebe.enoyolf.org>
Doug Maxey wrote:
> On Mon, 28 Jan 2008 14:04:51 EST, Konrad Rzeszutek wrote:
>>>> +EXPORT_SYMBOL(find_ibft);
>>> Is this x86-specific? Are suitable Kconfig dependencies in place?
>> Originally I had it to be x86-specific but was told that I should make it all
>> platforms since the IBFT is platform independent. Somebody can very well
>> insert a NIC with IBFT on a IA64 machine or PPC.
>
> I would beg to differ regarding the powerpc. On powerpc, the bios is
> invisible and ignored. We have our own "special" way, via the device-tree
> in procfs.
>
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.)
-hpa
next prev parent reply other threads:[~2008-01-28 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:06 [PATCH] Add iSCSI iBFT support (v0.4.5) 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 [this message]
2008-01-28 20:46 ` Konrad Rzeszutek
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=479E2E89.7030704@zytor.com \
--to=hpa@zytor.com \
--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=konrad@darnok.org \
--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 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.