From: Dan Malek <dan@mvista.com>
To: Stefan Roese <stefan.roese@esd-electronics.com>
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:20:26 -0400 [thread overview]
Message-ID: <3BAA093A.10E96272@mvista.com> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJEEMCDCAA.stefan.roese@esd-electronics.com
Stefan Roese wrote:
> Hmmm, now I am totally confused!
Me, too. I have more to do than just track the progress of this
patch, which is changing faster than I can read e-mail.
> #ifndef __CPCI405_H
> #define __CPCI405_H
>
> #include <linux/config.h>
>
> #include <asm/ppcboot.h>
>
> #endif /* __CPCI405_H */
This is fine, Tom said it was an empty file.........
> Tom convinced me to remove this header and so I changed ppc4xx.h this way:
This is fine, too, but certainly doesn't justify re-engineering the way
we handle all of the other embedded boards. Your board just happens to
take advantage of all of the generic 4xx definitions, so you don't need
anything else.
> ...... but I
> have to admit that I don't have a clue what is going to replace it (please
> have mercy with my ignorance ;-))! Can somebody enlighten me (link's, etc.)?
Just take a look at all of the bootloaders for all of the other platforms.
The 4xx and 8xx should have changed to look like these long ago. I just
didn't have time to do it, and no one else was interested.
> Dan, you are right that we (PPCBoot) people will have some homework to do,
> but right now our only way to Linux is via the bd_info struct!
No, the way to Linux is to _always_ use a zImage with an attached bootloader.
PPCboot can continue to pass whatever it wants, or the bootloader can find
the information in other ways as it does today with many boards. Booting
a vmlinux image and trying to keep track of that private interface between
the bootloader and the kernel is difficult. We already have more changes
planned in addition to the bi_recs interface. Much of the code found today
in the head.S files is going to migrate to the bootloaders.
> So please, is anybody willing to check this stuff into the
> linuxppc_2_4_devel tree (Tom, Dan)?
We are working on it. We all have real jobs to do besides trying to
manage all of these sources. I would like to get some of _my_ stuff
checked in as well.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-20 15:20 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 [this message]
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
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=3BAA093A.10E96272@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.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).