From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Val Henson <val@nmt.edu>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: SBS Palomar II/IV/V port
Date: Wed, 10 Oct 2001 23:30:37 +0200 [thread overview]
Message-ID: <20011010213037.30369@smtp.wanadoo.fr> (raw)
In-Reply-To: <20011010122415.A22918@boardwalk>
>Indeed! This is on my list of stuff to do - straighten out once and
>for all how BI_INITRD works and then rewrite the Gemini boot process
>to use it. It seemed like we had two interpretations:
>
>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 have no preference either way, I just want someone to tell me which
>way we're going to do it. :)
We can very easily support both ways. In the first case, we should
also clearly comment the fact that the pointer passed to the kernel
is physical.
I'll eventually push some code in the upcoming 1 or 2 days that
does the kernel-side of getting passed pointer-based birecs. I
will eventually throw in a couple of new birec definitions as
well.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-10 21:30 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 [this message]
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
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=20011010213037.30369@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=val@nmt.edu \
/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).