From: Mike Ditto <mditto@consentry.com>
To: Daniel Ng <daniel.ng1234@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: How to bring up fs_enet on 2.6.27?
Date: Wed, 25 Feb 2009 01:25:59 -0800 [thread overview]
Message-ID: <49A50EA7.8040008@consentry.com> (raw)
In-Reply-To: <547eba1b0902242309o2086dce2p49c59a9ea1b85b53@mail.gmail.com>
Daniel Ng wrote:
>> Now, I'm seeing these boot messages:
>>
>> f0010d40:00 not found
>> eth0: Could not attach to PHY
Daniel,
These messages are typical of having the wrong GPIO pins in the mdio
node or the wrong MDIO address (reg property) in the ethernet-phy node.
>> Currently, our PHY
>> attributes eg. 'auto-negotiate' are not changeable, so we aren't
>> actually using MDC+MDIO even the MDC+MDIO lines exist.
The driver definitely tries to talk to the PHY using the GPIO pins
and address specified and if it doesn't respond, it won't attach.
>> Also, the PHY
>> interrupt line is not wired up. Hence the PHY0 interrupts field is <0
>> 8> (or should it be removed altogether?).
The mdio driver works without interrupts. I have no interrupt-parent
or interrupts properties on my ethernet-phy node.
-=] Mike [=-
next prev parent reply other threads:[~2009-02-25 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1233190802.9523.linuxppc-dev@ozlabs.org>
2009-01-29 1:16 ` How to bring up fs_enet on 2.6.27? Mike Ditto
2009-02-19 6:47 ` Daniel Ng
2009-02-19 18:44 ` Scott Wood
2009-02-20 5:01 ` Daniel Ng
2009-02-25 7:09 ` Daniel Ng
2009-02-25 9:25 ` Mike Ditto [this message]
2009-02-27 6:41 ` Daniel Ng
2009-03-04 21:00 ` Scott Wood
2009-01-28 5:04 Daniel Ng
2009-01-28 9:50 ` Laurent Pinchart
2009-01-29 0:42 ` Daniel Ng
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=49A50EA7.8040008@consentry.com \
--to=mditto@consentry.com \
--cc=daniel.ng1234@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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.