From: Benjamin Herrenschmidt <bh40@calva.net>
To: Cort Dougan <cort@fsmlabs.com>,
linuxppc-dev@lists.linuxppc.org, paulus@linuxcare.com
Subject: Re: bootloader & head.S weirdness (patch)
Date: Tue, 23 Nov 1999 11:40:01 +0100 [thread overview]
Message-ID: <19991123114001.002761@mailhost.mipsys.com> (raw)
In-Reply-To: <19991122144054.C12973@hq.fsmlabs.com>
On Mon, Nov 22, 1999, Cort Dougan <cort@fsmlabs.com> wrote:
>I'll check this patch with the latest 2.2 to see how it goes. Would using
>the bootinfo structure we talked about a few weeks ago help? I'd like to
>unify things a bit with it but I'm not sure how many problems it would
>solve and how many it could cause.
I'd really like to see this happen. There is really an urgent need to
cleanup the mess with initrd and the way the command line is passed to
the kernel too and this would get rid of those.
There is one idea suggested to me by Gabriel Paubert which would be worth
considering:
Define some kind of bootx-like bootinfo structure (will all addresses
relative to the beginning of the structure) and move out of the kernel
_all_ those head.S hacks AND all the prom_init code (reading the OF tree,
initing the display, instanciating RTAS, ...).
All this would be done from a head-appended bootloader which would built
a device tree when OF is available, and then enter the kernel with a
unified entry point based on a structure, known mappings.
I don't know if it's worth doing that _now_ (it involves almost breaking
everything), but I like the idea of cleaning all this up.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-23 10:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19991122120429.031138>
1999-11-22 11:47 ` bootloader & head.S weirdness (patch) Benjamin Herrenschmidt
1999-11-22 17:07 ` Benjamin Herrenschmidt
1999-11-22 22:06 ` Cort Dougan
1999-11-23 10:44 ` Benjamin Herrenschmidt
1999-11-23 12:35 ` Benjamin Herrenschmidt
1999-11-22 21:40 ` Cort Dougan
1999-11-23 10:40 ` Benjamin Herrenschmidt [this message]
1999-11-23 17:48 ` Cort Dougan
1999-11-23 18:34 ` Geert Uytterhoeven
1999-11-23 19:16 ` Cort Dougan
1999-11-23 19:35 ` Benjamin Herrenschmidt
1999-11-23 20:16 ` Geert Uytterhoeven
1999-11-23 20:21 ` Cort Dougan
1999-11-24 7:32 ` Geert Uytterhoeven
[not found] <19991123133536.013861>
1999-11-23 17:07 ` Benjamin Herrenschmidt
1999-11-23 17:52 ` Cort Dougan
1999-11-23 18:08 ` Benjamin Herrenschmidt
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=19991123114001.002761@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=cort@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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).