From: Tom Rini <trini@kernel•crashing.org>
To: Magnus Damm <damm@opensource•se>
Cc: Cort Dougan <cort@fsmlabs•com>, linuxppc-embedded@lists•linuxppc.org
Subject: Re: bi_record and initrd
Date: Mon, 18 Nov 2002 10:13:58 -0700 [thread overview]
Message-ID: <20021118171358.GA17957@opus.bloom.county> (raw)
In-Reply-To: <3DD8A28C.E8EABFF@opensource.se>
On Mon, Nov 18, 2002 at 09:19:24AM +0100, Magnus Damm 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.
>
> So, the following registers passed to the kernel could change from
>
> * r3: ptr to board info data
> * r4: initrd_start or if no initrd then 0
> * r5: initrd_end - unused if r4 is 0
> * r6: Start of command line string
> * r7: End of command line string
In arch/ppc/boot, only r3 is used now, FWIW.
> to
>
> * r3: ptr to bi_record
Or so, yes. Look at the archives for discussions / flamewars about
bi_records.
> If the initrd is going to be passed with the bi_record, and the command line
> already is there, then it's just the board info left. (for the 8xx anyhow)
The initrd already is, right now. And yes, the bd_t would be passed, or
phased out, see the above mentioned discussions / flamewars.
> Or maybe there are zillions of applications booting the kernel directly
> without the bootloader..
Something _always_ loads the kernel someplace. Call it what you will,
but the thing moving the kernel to 0 and pressing go is the bootloader.
Oh, and see the above mentioned discissions / flamewars :)
--
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 17:13 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 [this message]
2002-11-19 4:29 ` Murray Jensen
2002-11-18 14:19 ` Tom Rini
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=20021118171358.GA17957@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=cort@fsmlabs$(echo .)com \
--cc=damm@opensource$(echo .)se \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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