From: Wolfgang Denk <wd@denx.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org, "Mehlan,
Markus \(Ritter Elektronik\)"
<markus.mehlan@ritter-elektronik.de>
Subject: Re: [MPC5200] problem running FEC and ATA
Date: Wed, 23 Jan 2008 01:20:40 +0100 [thread overview]
Message-ID: <20080123002040.5049F24781@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 21 Jan 2008 17:28:22 +0100." <200801211728.22817.jbe@pengutronix.de>
In message <200801211728.22817.jbe@pengutronix.de> you wrote:
>
> Is anybody out there with more MPC5200B experience? Can someone tell me why
> some MPC5200B are need this patch and others not? We have two different
> systems here (cards from different vendors) with the same processor, one
> needs this BSDIS-patch and the other not. ???????????????
Is it really exactly the same CPU revision? My guess is that one is
rev. B and the other one is older...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It would be illogical to assume that all conditions remain stable
-- Spock, "The Enterprise" Incident", stardate 5027.3
next prev parent reply other threads:[~2008-01-23 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 7:10 [MPC5200] problem running FEC and ATA Mehlan, Markus (Ritter Elektronik)
2008-01-21 8:57 ` Juergen Beisert
2008-01-21 13:01 ` Mehlan, Markus (Ritter Elektronik)
2008-01-21 16:28 ` Juergen Beisert
2008-01-23 0:20 ` Wolfgang Denk [this message]
2008-01-23 6:53 ` Mehlan, Markus (Ritter Elektronik)
2008-01-23 22:58 ` Wolfgang Denk
2008-01-23 9:03 ` Juergen Beisert
2008-01-23 23:01 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 13:24 Arnon Kaufman
2007-12-16 15:44 ` Robert Schwebel
2007-12-16 17:28 ` Arnon Kaufman
2007-12-16 17:46 ` Robert Schwebel
2007-12-18 10:41 ` Juergen Beisert
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=20080123002040.5049F24781@gemini.denx.de \
--to=wd@denx.de \
--cc=jbe@pengutronix.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=markus.mehlan@ritter-elektronik.de \
/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).