linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: MPC5200 and Bestcomm
Date: Mon, 13 Aug 2007 12:27:19 -0400	[thread overview]
Message-ID: <9e4733910708130927l70163a80vf0362ee8649a6c29@mail.gmail.com> (raw)

We're starting a new MPC5200 project and I'm trying to track down the
best kernel to start from. Is Sylvain's tree at
http://www.246tnt.com/mpc52xx/ a good place to start? The git URLs
from the web page don't work. Everything 5200 related in the trees at
Secret Labs already appears to be merged.

Most of this work also appears to be in the Open Embedded tree's Ekifa
support. Is that a better place to start?

I need to get multiple I2S ports running with DMA.

-- 
Jon Smirl
jonsmirl@gmail.com

             reply	other threads:[~2007-08-13 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 16:27 Jon Smirl [this message]
2007-08-13 16:34 ` MPC5200 and Bestcomm Grant Likely
2007-08-13 16:50   ` Jon Smirl
2007-08-13 16:52     ` Jon Smirl
2007-08-13 17:43       ` Matt Sealey
2007-08-13 18:32         ` Jon Smirl
2007-08-13 17:15   ` Bartlomiej Sieka

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=9e4733910708130927l70163a80vf0362ee8649a6c29@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --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).