From: Dan Malek <dan@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
Linuxppc-Commit <linuxppc-commit@source.mvista.com>
Subject: Re: CPCI-405 port (PPC405GP)
Date: Thu, 20 Sep 2001 11:34:41 -0400 [thread overview]
Message-ID: <3BAA0C91.42E0910D@mvista.com> (raw)
In-Reply-To: 20010920075537.A13721@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
> Well, because it keeps us from duplicating 4 lines in the makefile.
OK.
> ..... CONFIG_TREEBOOT could probably die, unless
> someone revives Oak or TiVo uses it.
Walnut and Spruce use it. Get it? TREEboot?
> Not in 2.4 we aren't. We aren't forcing bi_recs upon everyone just
> yet.
We should. The purpose of consolidating bootloaders was to utilize
a bunch of generic code on both sides (bootloader and Linux). It
isn't a major change on either side, since we already have bootloaders
that do it.
> Eh? As far as I know, PPCBoot takes it's own slighlty mod'ed objcopy'ed
> and gzip'ed vmlinux. What's wrong with that?
We (or at least I :-) make subtle changes to the parameters passed to
the kernel from the bootloaders from time to time. This means people
with PPCboot roms have to change them any time this is done. One of
the purposes of the bootloader is to isolate these changes into the
bootloader.
> .... Hell, even in 2.5 as long
> as we get the bi_recs, we shouldn't care what the bootloader does..
The bootloader is a critical part to initializing the environment for
the kernel. With all of the MMU futzing around we do trying to get
Linux running, Ben and I have discussed yet another better bootloader
method to move some of this around between the bootloader and the
kernel start up. There are also initrd and command line things done
by the bootloader (among other board specific initialization). It's
more than whether or not we all use bi_recs.
> Are you talking about the board-specific stuff .....
Never mind. Not important.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-20 15:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EFEAIMDCOOOHIEPHDNFJEEENDCAA.stefan.roese@esd-electronics.com>
2001-09-10 17:13 ` CPCI-405 port (PPC405GP) Dan Malek
2001-09-11 7:15 ` AW: " Stefan Roese
2001-09-11 17:36 ` Matthew Locke
2001-09-11 17:53 ` Dan Malek
2001-09-12 13:12 ` AW: " Stefan Roese
2001-09-18 18:57 ` Tom Rini
2001-09-19 13:46 ` Stefan Roese
2001-09-19 14:17 ` Tom Rini
2001-09-19 15:55 ` AW: " Stefan Roese
2001-09-19 18:10 ` Dan Malek
2001-09-19 22:57 ` Tom Rini
2001-09-19 23:02 ` Dan Malek
2001-09-19 23:31 ` Tom Rini
2001-09-20 4:12 ` Dan Malek
2001-09-20 9:20 ` Stefan Roese
2001-09-20 15:20 ` Dan Malek
2001-09-20 15:46 ` Tom Rini
2001-09-20 21:43 ` Dan Malek
2001-09-20 21:56 ` Tom Rini
2001-09-21 7:04 ` Geert Uytterhoeven
2001-09-21 13:55 ` Tom Rini
2001-09-23 18:01 ` Wolfgang Denk
[not found] ` <3BAEB9DA.232C8FEB@mvista.com>
2001-09-29 15:34 ` Dan Malek
2001-09-20 14:55 ` Tom Rini
2001-09-20 15:34 ` Dan Malek [this message]
2001-09-20 15:51 ` Tom Rini
2001-09-20 16:10 ` Mark Hatle
2001-09-20 21:38 ` Dan Malek
2001-09-23 18:01 ` Wolfgang Denk
2001-09-23 20:54 ` Tom Rini
2001-09-20 14:59 ` Josh Huber
2001-09-20 15:39 ` Dan Malek
2001-09-20 15:57 ` Josh Huber
2001-09-20 16:07 ` Tom Rini
2001-09-20 16:32 ` Josh Huber
2001-09-20 16:35 ` Tom Rini
2001-09-23 18:00 ` Wolfgang Denk
2001-09-23 20:50 ` Tom Rini
2001-09-24 4:04 ` Dan Malek
2001-09-23 18:00 ` Wolfgang Denk
2001-09-20 8:00 ` Stefan Roese
2001-09-19 14:32 ` Stefan Roese
[not found] <3BAEB761.194CE057@mvista.com>
2001-09-29 7:53 ` Wolfgang Denk
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=3BAA0C91.42E0910D@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).