From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Stefan Strobl <nst@gersys.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Problem Ethernet Initialization MPC5200 + LXT971A
Date: Mon, 08 Nov 2010 17:50:58 +0800 [thread overview]
Message-ID: <4CD7C802.8020908@windriver.com> (raw)
In-Reply-To: <4CD431B4.7060405@gersys.de>
Stefan Strobl wrote:
> Hi
>
> I'm having a Problem with the Initialization of my Ethernet PHY
> (FEC_MPC5200 + LXT971A Phy). I'm using latest U-Boot and Linux 2.6.37
> from Denx.
>
> Once in Linux I can ping my own IP-Address but not any other device in
> my network. The Link LED is on when connected to the network but when
> pinging some other device nothing is being transmitted (Traffic LED is
> off).
>
> If - before booting - I'm using any network command under U-Boot (which
> is calling eth_init()), the interface works fine after that under Linux
> also!
> In that case the kernel prints the line:
> PHY: f003000:00 - Link is Up - 100/Full
Can you probe PHY successfully when failed?
>
> So I'm not sure whether the Linux driver does not initialize the PHY
> correctly or whether I should be running a command under Linux that
> makes the interface work. I've played around with ifconfig but that
> didn't get me any further.
>
> Under sysfs I can see that the MAC address is assigned correctly but:
> carrier = 0 (should be 1)
> duplex = half (should be full)
> operstate = down
> speed = 10 (should be 100)
>
Can you use 'ethtool' utility to access/control that? If no please check how you
access PHY by MII bus? I doubts some multiplex PIN should be configured when you
operate PHY.
> To workaround I could make u-boot run eth_init() always but that doesn't
> seem the right approach to this.
Yes. Often we shouldn't depend the bootloader do this when we use NIC. But its
worth tracking eth_init in detail to check what are missed for Linux. I guest
those should be dedicated to the hardware. For example, configuring
multiplex-pin, or reset PHY before the real operation action and so on.
Tiejun
>
> Any ideas?
>
> Many Thanks,
> Stefan.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2010-11-08 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 16:32 Problem Ethernet Initialization MPC5200 + LXT971A Stefan Strobl
2010-11-08 9:50 ` tiejun.chen [this message]
2010-11-08 13:25 ` Stefan Strobl
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=4CD7C802.8020908@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nst@gersys.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 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.