From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Cc: paulus@samba.org, val@nmt.edu
Subject: Re: SBS Palomar II/IV/V port
Date: Wed, 10 Oct 01 13:13:38 PDT [thread overview]
Message-ID: <0110102013.AA25096@ivan.Harhan.ORG> (raw)
Val Henson <val@nmt.edu> wrote:
> 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. :)
I really need to be able to have the initrd image located anywhere, forcing it
to be part of the bi_recs list is unacceptable. But if someone really wants
option 2, maybe we can have two different bi_recs to suit everyone?
--
Michael Sokolov 5791 VAN ALLEN WAY
Software Engineer CARLSBAD CA 92008-7321 USA
SBS Technologies, Inc. Phone: +1-760-438-6900 x2347
Communications Products or 1-888-SBS-COMM x2347
Fax: +1-760-438-6985
E-mail: msokolov@sbs.com
or msokolov@ivan.Harhan.ORG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-10 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 20:13 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 1:53 SBS Palomar II/IV/V port Michael Sokolov
[not found] <0110092125.AA22665@ivan.Harhan.ORG>
2001-10-10 18:24 ` 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
2001-10-11 23:18 ` Tom Rini
2001-10-12 16:26 ` Peter Bergner
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=0110102013.AA25096@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).