From: Peter Bergner <bergner@brule.borg.umn.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SBS Palomar II/IV/V port
Date: Thu, 11 Oct 2001 08:11:23 -0500 [thread overview]
Message-ID: <20011011081123.B278838@brule.borg.umn.edu> (raw)
In-Reply-To: <20011010180622.B11067@cpe-24-221-152-185.az.sprintbbd.net>
On Wed, Oct 10, 2001 at 06:06:22PM -0700, Tom Rini wrote:
: > 1. The BI_INITRD boot record contains the start address and the size
: > of the initrd.
: >
: > 2. The BI_INITRD boot record contains the entire initrd itself (as a
: > really large boot record).
:
: I thought we had agreed on 1 (and nothing uses it yet anyhow). Tho my
: memory could be hazy.
This was my understanding as well of the earlier conversations,
so this is what I used to implement zImage.initrd for ppc64.
Hopefully everyone remembers this not only affects the ppc32
kernel, but also affects the ppc64 kernel as well.
Peter
--
Peter Bergner
SLIC Optimizing Translator Development / Linux PPC64 Kernel Development
IBM Rochester, MN
bergner@vnet.ibm.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-11 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0110092125.AA22665@ivan.Harhan.ORG>
2001-10-10 18:24 ` SBS Palomar II/IV/V port Val Henson
2001-10-10 21:30 ` Benjamin Herrenschmidt
2001-10-11 1:05 ` Tom Rini
2001-10-10 23:57 ` Paul Mackerras
2001-10-11 1:06 ` Tom Rini
2001-10-11 13:11 ` Peter Bergner [this message]
2001-10-11 23:18 ` Tom Rini
2001-10-12 16:26 ` Peter Bergner
2001-10-10 20:13 Michael Sokolov
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 1:53 Michael Sokolov
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=20011011081123.B278838@brule.borg.umn.edu \
--to=bergner@brule.borg.umn.edu \
--cc=bergner@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).