From: David Hawkins <dwh@ovro.caltech.edu>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PowerQUICC II Pro MPC8349E-MDS Linux 2.6 support
Date: Wed, 15 Feb 2006 16:01:22 -0800 [thread overview]
Message-ID: <43F3C0D2.3000207@ovro.caltech.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0602151743030.450-100000@gate.crashing.org>
>> ... for the MPC8349E-MDS board?
>
> Yes, Freescale names the board four different things durings its
> development (ADS, SYS, MDS, ok maybe only three :)
Ok, great.
>>In the Denx source, there is modified versions for the
>>TQM board, but I wasn't sure what platform the original
>>files were targeted for.
>
> Not sure, I follow. The MPC834x MDS was the first 834x system supported.
Sorry, my fault, I wasn't clear.
I was just referring to the fact that in addition to your
source, the Denx tree also has the work they are doing on
the TQM board that contains an 8349E.
> However, if you are looking at 834x, I recommend you grab my u-boot tree
> from kernel.org since it has support for booting the kernel with a flat
> device tree. From 2.6.16, all future 83xx work will be done in
> arch/powerpc which requires a flat dev tree to boot.
Ok.
The reason I was asking, was that I want to benchmark an 8349E
based system. Wolfgang Denx mentioned the TQM system, so I took
a look in the Denx tree, and saw that their work was based
on yours. I assumed your work was for a Freescale reference board,
but didn't know which.
Thanks for the clarification.
Dave
prev parent reply other threads:[~2006-02-16 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 22:06 Cache-inhibited region for certain exception handler(e500 chips, 2.4 kernel)? Xianghua Xiao
2006-02-15 23:25 ` Kumar Gala
2006-02-15 23:50 ` PowerQUICC II Pro MPC8349E-MDS Linux 2.6 support David Hawkins
2006-02-15 23:45 ` Kumar Gala
2006-02-16 0:01 ` David Hawkins [this message]
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=43F3C0D2.3000207@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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).