From: Kumar Gala <galak@kernel.crashing.org>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PowerQUICC II Pro MPC8349E-MDS Linux 2.6 support
Date: Wed, 15 Feb 2006 17:45:25 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0602151743030.450-100000@gate.crashing.org> (raw)
In-Reply-To: <43F3BE4A.7070603@ovro.caltech.edu>
On Wed, 15 Feb 2006, David Hawkins wrote:
>
> Hi Kumar,
>
> I saw your email earlier, so figured you were listening in
> on the PPC group at the moment.
>
> In the recent 2.6 kernel source, you authored the file:
>
> arch/ppc/platforms/83xx/mpc834x_sys.h and .c
>
> are these files for the MPC8349E-MDS board?
Yes, Freescale names the board four different things durings its
development (ADS, SYS, MDS, ok maybe only three :)
> 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.
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.
- kumar
next prev parent reply other threads:[~2006-02-15 23:54 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 [this message]
2006-02-16 0:01 ` David Hawkins
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=Pine.LNX.4.44.0602151743030.450-100000@gate.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dwh@ovro.caltech.edu \
--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).