From: Peter Pan <pppeterpppan@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: My MDIO is acting strange
Date: Fri, 23 Apr 2010 10:36:48 +0800 [thread overview]
Message-ID: <x2v48abf2c21004221936kf5ca0a49mbf476d379038568@mail.gmail.com> (raw)
I'm porting Linux 2.6.32.6 to my MPC8247 based board. Our FCC1 and
FCC2 are used as 100MBps ethernet ports. MDIO is used to connect with
PHY chip. During boot, the of driver is checking the PHYID, it gets
all Fs. But after I comment the following lines:
//if ((phy_id & 0x1fffffff) == 0x1fffffff)
// return NULL;
I can use my FCC ethernet normally after boot into console.
I checked that while boot, all the read bit from MDIO pin is 1, that
makes no TA bit, and no PHYID.
I'm wondering why is that happening.
next reply other threads:[~2010-04-23 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 2:36 Peter Pan [this message]
[not found] ` <z2m2acbd3e41004230814pc0ce9acasaf99a180d3f5b702@mail.gmail.com>
2010-04-23 15:32 ` My MDIO is acting strange Peter Pan
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=x2v48abf2c21004221936kf5ca0a49mbf476d379038568@mail.gmail.com \
--to=pppeterpppan@gmail.com \
--cc=linuxppc-dev@lists.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).