From: Dan Malek <dan@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Stefan Roese <stefan.roese@esd-electronics.com>,
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 17:43:10 -0400 [thread overview]
Message-ID: <3BAA62EE.2006422D@mvista.com> (raw)
In-Reply-To: 20010920084607.D13721@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
> .... In some parts of the PPC world, we can't/don't for various
> reasons (technical and/or ingrained).
I can't think of any that don't......Help me remember :-).
> .... For example, I don't see a problem
> with something which takes a vmlinux.gz and boots it.
First of all, someone has to uncompress it. Then someone has
to handle any initrd loading. Then someone has to handle command line
and other parameter passing. Then.....
> .... But we should define what we're going to do before we do
> it so that yaboot/ppcboot and apus can figure out how much re-working
> they'll need and whatnot..
Well, I trusted Ben to provide some of this information. Mind you,
it was only a few lines on IRC, but it started with moving all of
the cputable initialization stuff into the bootloaders......and went
downhill from there :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-20 21:43 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 [this message]
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
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=3BAA62EE.2006422D@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.com \
--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).