From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Allen Kennedy Jr." <allen@kennedystuff.com>
Cc: barebox@lists.infradead.org
Subject: Re: Porting to a new board
Date: Sat, 21 Sep 2013 09:50:47 +0200 [thread overview]
Message-ID: <20130921075047.GJ30088@pengutronix.de> (raw)
In-Reply-To: <CAO-21LOxC24toR=vwTJFx1RrkKX0U-cgbZXjh8UOhznm08Rv0Q@mail.gmail.com>
On Fri, Sep 20, 2013 at 04:02:44PM -0500, Allen Kennedy Jr. wrote:
> Thanks for the great idea to start with a loaded image in ram.
>
> I was able to get it to run, but I can't get the Ethernet to work.
> I'm not entirely sure where to begin looking.
>
> I hit devinfo and get:
> <snip>
> `---- imx27-fec
> `---- miibus0
> `---- eth0
> <...>
> drivers:
> <...>
> SMSC LAN83C185
> SMSC LAN8187
> SMSC LAN8700
> SMSC LAN911x Internal PHY
> SMSC LAN8710/LAN8720
> fec_imx
> Generic PHY
> </snip>
>
> This would seem to indicate to me that the drivers are loading. And
> that the register happened.
> But I'm not sure where to go from here.
What's the output of some network command, like for example 'dhcp'?
What's the output of 'md -w -s /dev/phy0'?
Problems with networking usually go down to problems with the phy.
What's the content of the platform data for the FEC? It should look
like:
static struct fec_platform_data fec_info = {
.xcv_type = PHY_INTERFACE_MODE_MII,
.phy_addr = -1,
};
With xcv_type being MII (I think it's the only possibility on i.MX27)
and phy_addr to either -1 for autodetecting the address or the correct
address. Use -1 to be on the safe side.
When 'md -w -s /dev/phy0' doesn't show any sensible register output then
your pinmux may be wrong or you haven't brought your phy out of reset
with some gpio.
>
> In another thread... the advice was given to check the MII address,
> although I'm not sure how to interpret the data sheet.
> It looks as though the address is 31. But I could be wrong. When I
> try 31, and do a DHCP the processor hangs.
> So I tried 0, and the processor hangs.
>
> Is there a "scan the bus mode" I can use in the fec driver? I don't
> see one, but I may be looking in the wrong spot.
It's not in the FEC driver but in the generic MII support. As said, use
-1 as phy id.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-09-21 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 21:44 Allen Kennedy Jr.
2013-09-19 7:35 ` Sascha Hauer
2013-09-20 21:02 ` Allen Kennedy Jr.
2013-09-21 7:50 ` Sascha Hauer [this message]
2013-09-23 21:47 Allen Kennedy Jr.
2013-09-24 4:24 ` Antony Pavlov
2013-09-24 7:39 ` Sascha Hauer
2013-09-24 15:00 ` Allen Kennedy Jr.
2013-09-24 16:33 ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-24 17:06 ` Allen Kennedy Jr.
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=20130921075047.GJ30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=allen@kennedystuff.com \
--cc=barebox@lists.infradead.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