From: Tom Rini <trini@kernel.crashing.org>
To: Cort Dougan <cort@fsmlabs.com>
Cc: Magnus Damm <damm@opensource.se>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: bi_record and initrd
Date: Mon, 18 Nov 2002 07:19:49 -0700 [thread overview]
Message-ID: <20021118141949.GB15279@opus.bloom.county> (raw)
In-Reply-To: <20021115100857.H9673@duath.fsmlabs.com>
On Fri, Nov 15, 2002 at 10:08:57AM -0700, Cort Dougan wrote:
> This would be a good opportunity to switch-over to allowing the bootloader
> stick the initrd where it wants and just pass the physical pointer in via
> bi_record in all cases. It would certainly simplify these cases.
I'm not so sure. In the case of arch/ppc/boot/ and not on OF, there
aren't many places we really know are 'good' that we can throw things.
I think what might help, and that we can do in 2.5 even, is allow the
bootloader to put the bi_recs wherever it wants to, pass that along in
r3 or r4 or so, and then in this case, we would align the bi_recs at
_ALIGN(0+zimage)+_ALIGN(initrd), and if that's > 8MB, make sure that we
don't allow the end of the initrd to be overwritten too.
And keep in mind it's Monday, and I haven't had any coffee yet, if
there's any horribly silly mistakes above :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-18 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 15:54 bi_record and initrd Magnus Damm
2002-11-14 17:48 ` Tom Rini
2002-11-15 12:02 ` Magnus Damm
2002-11-15 17:08 ` Cort Dougan
2002-11-18 8:19 ` Magnus Damm
2002-11-18 17:13 ` Tom Rini
2002-11-19 4:29 ` Murray Jensen
2002-11-18 14:19 ` Tom Rini [this message]
2002-11-19 18:11 ` Tom Rini
2002-11-19 18:19 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 21:00 Richard Laing
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=20021118141949.GB15279@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=cort@fsmlabs.com \
--cc=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.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