From: Kim Phillips <kim.phillips@freescale.com>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Anyone using mpc832x_mds & freescale's GIT repo?
Date: Tue, 1 May 2007 09:00:06 -0500 [thread overview]
Message-ID: <20070501090006.4c9f5723.kim.phillips@freescale.com> (raw)
In-Reply-To: <46370991.3010802@cambridgebroadband.com>
On Tue, 01 May 2007 10:34:09 +0100
Alex Zeffertt <ajz@cambridgebroadband.com> wrote:
>
> mention above. Do you know which *linux* repository is the most
> current for the MPC8323E-MDS-PB board?
yes, linux..normally I'd say paulus' powerpc.git tree on kernel.org, but
today, 832x-MDS is broken there. You might want to checkout the v2.6.21
tag until the pending patches (to support the ucc phylib) are applied and
merged.
Kim
next prev parent reply other threads:[~2007-05-01 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:15 Anyone using mpc832x_mds & freescale's GIT repo? Alex Zeffertt
2007-04-30 18:52 ` Kim Phillips
2007-05-01 9:34 ` Alex Zeffertt
2007-05-01 14:00 ` Kim Phillips [this message]
2007-05-01 14:05 ` Alex Zeffertt
2007-05-01 14:26 ` Kim Phillips
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=20070501090006.4c9f5723.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=ajz@cambridgebroadband.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).