From: NM <therealshowman@yahoo.ca>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8272 FCC2 MDIO on Port D and FS_ENET
Date: Mon, 11 Feb 2008 17:04:56 -0500 (EST) [thread overview]
Message-ID: <231618.80613.qm@web32710.mail.mud.yahoo.com> (raw)
In-Reply-To: <47B0C099.5030205@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
Thanks Scott,
I do boot from U-BOOT, via Ethernet, but I'd never set the MDIO/MDC in U-BOOT. Actually, looking at the u-boot 's MPC8260ADS.h now, it is still setting the default 8272ADS boards' PC18/19 for MDC/MDIO - and my unit is using PD23/29.
I guess U-BOOT is probably working (for me) since it probably defaults to the defaults of PHY and maybe not checking for PHY errors???
I guess, it is probably worthwhile having the MDIO/MDC pins also set up explicitly in mpc8272_ads_pins as opposed to relying on the boot loader.
Scott Wood <scottwood@freescale.com> wrote: NM wrote:
> My problem is solved now after probing the lines, MDC was not showing
> any activity.
> So, after explicitly setting the PD23 (MDC) to : OUTPUT/GPIO in
> mpc8272_ads_pins and it worked in
>
> I'd previously thought about that, but I was sure that this was being
> taken care of, but now that I'm thinking of it, I'm questioning my belief.
> I think in the fs_enet/mii-bitbang.c: mdio_dir(..) it is supposed to
> take care of this.
No, the mdc pin is static; only bits which need to be changed
dynamically are dealt with in mii-bitbang.c. Either the firmware or the
platform code should set up static pins.
> But why I had to explictly set it initially beats me.
> I wonder how this works in standard distribution.
It's probably set up by u-boot normally, at least if you boot from ethernet.
-Scott
---------------------------------
Looking for the perfect gift? Give the gift of Flickr!
[-- Attachment #2: Type: text/html, Size: 1823 bytes --]
prev parent reply other threads:[~2008-02-11 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 19:45 MPC8272 FCC2 MDIO on Port D and FS_ENET Show Man
2008-02-11 21:26 ` NM
2008-02-11 21:39 ` Scott Wood
2008-02-11 22:04 ` NM [this message]
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=231618.80613.qm@web32710.mail.mud.yahoo.com \
--to=therealshowman@yahoo.ca \
--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 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.