From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: linuxppc-embedded@ozlabs.org
Cc: Stefan Nickl <stefan.nickl@kontron.com>
Subject: Re: Which PHY connection to use on MPC8541...
Date: Wed, 12 Oct 2005 08:43:43 +0200 [thread overview]
Message-ID: <200510120843.43750.g.jaeger@sysgo.com> (raw)
In-Reply-To: <4BD1885F-AD59-4FFF-8694-AB66BE80DF96@freescale.com>
On Tuesday 11 October 2005 20:05, Andy Fleming wrote:
> On Oct 11, 2005, at 05:57, Stefan Nickl wrote:
> > Hi,
> >
> > about a year ago we resorted to using port pin MDIO in this situation
> > for the FCCs because the fcc_enet driver and the gianfar driver live
> > in separate worlds, so to speak.
> >
> > But in the meantime, Andy Fleming was very active regarding the PHY
> > abstraction layer. I still haven't seen patches that migrate fcc_enet
> > to using this layer, but the gianfar driver seems to use this code
> > now.
> >
> The work to migrate the new fs_enet driver to use the TSEC MDIO is in
> progress. I have a few other things I'm working on right now, and
> I've been having some hardware issues, but I've already done most of
> the work to get the FCC to use the TSEC's MDIO bus.
> >
> > So I'd say quick solution: use TSEC1 MDIO for TSECs and cpm port pins
> > for FCC, clean solution: change fcc_enet to use the PHY abstraction
> > layer.
> >
> I'd say it depends on how long until your hardware is ready. You
> might want to wire up the cpm IO pins, just in case. I have yet to
> actually get the fs_enet driver to send packets on the 8560, so
> there's no telling how long it will be before that driver works on 8541.
>
> Andy
>
Thank you guys for the quick answers. We already thought of additionally
wireing up the cpm IO pins to have some kind of backup ;) We expect the
hardware to be available in february/march next year so I guess there's
pretty much time.
Gerhard
next prev parent reply other threads:[~2005-10-12 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 10:57 Which PHY connection to use on MPC8541 Stefan Nickl
2005-10-11 18:05 ` Andy Fleming
2005-10-12 6:43 ` Gerhard Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-11 10:13 Gerhard Jaeger
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=200510120843.43750.g.jaeger@sysgo.com \
--to=g.jaeger@sysgo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=stefan.nickl@kontron.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.