From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SMSC LAN8720 support
Date: Tue, 09 Feb 2010 12:59:03 -0800 [thread overview]
Message-ID: <4B71CC97.2090500@gmail.com> (raw)
In-Reply-To: <e0656fd71002091211s10b847d4h4afc11fe192cb823@mail.gmail.com>
Hi Maxim,
Two housekeeping items:
1. Please don't top-post
2. Please CC the mailing list. There are others that may be able to
help you.
On 2/9/2010 12:11 PM, Maxim Podbereznyi wrote:
> Hi Ben!
>
> Thank you for answering!
>
> Unfortunately I don't have any other board to check the Ethernet. I
> began to check sources and found that PHY ID is not read well.
>
> In the following code I have "No PHY present" on the console:
> /* Check if the PHY is up to snuff... */
> phy_id = macb_mdio_read(macb, MII_PHYSID1);
> if (phy_id == 0xffff) {
> printf("%s: No PHY present\n", netdev->name);
> return 0;
> }
> }
>
> I think at least ID must be read well. Bad luck :(
>
>
Are you passing the correct PHY address as parameter 3 to
macb_eth_initialize()? You should know the address from the board
schematic. Alternatively, it appears that MACB has an option called
CONFIG_MACB_SEARCH_PHY that will probe the MDIO bus. You might wish to
enable that option.
The MII_PHYSID1 is an IEEE 802.3-specified register. If you can't read
it, it's not anything peculiar to the new type of PHY, but more likely a
hardware/bootstrap issue. Any incompatibilities with this PHY will
come later when you try to configure some of the less-standard things
such as RGMII etc.
regards,
Ben
next prev parent reply other threads:[~2010-02-09 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 21:32 [U-Boot] SMSC LAN8720 support Maxim Podbereznyi
2010-02-08 20:55 ` Ben Warren
[not found] ` <e0656fd71002091211s10b847d4h4afc11fe192cb823@mail.gmail.com>
2010-02-09 20:59 ` Ben Warren [this message]
2010-02-09 21:04 ` Maxim Podbereznyi
2010-02-09 21:07 ` Ben Warren
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=4B71CC97.2090500@gmail.com \
--to=biggerbadderben@gmail.com \
--cc=u-boot@lists.denx.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