From: Heiko Schocher <hs@denx.de>
To: wael showair <showair2003@yahoo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: eth0: Could not attach to PHY
Date: Thu, 22 Jan 2009 10:17:07 +0100 [thread overview]
Message-ID: <49783993.4090408@denx.de> (raw)
In-Reply-To: <mailman.1613.1232571316.4534.linuxppc-dev@ozlabs.org>
Hello wael,
wael showair <showair2003@yahoo.com> wrote:
> i have a board with MPC8555 processor
> uboot version 1.1.6
> linux kernel 2.6.19-rc5
> ltib version: 6.2.2-sv
> gcc 3.4.3
>
> it boots successfully
> i want to upgrade my linux kernel to 2.6.27
> i upgraded the following:
> ltib version 8.1.2-sv
> gcc 4.1
> linux kernel 2.6.27
> & i kept the uboot with the same version 1.1.6
>
> the kernel booting stucks as follows:
>
> *****************************************************************************
> U-Boot 1.1.6 (Feb 8 2007 - 14:00:17)
[...]
> RPC: Registered tcp transport module.
> 24520:10 not found
> eth0: Could not attach to PHY
Here is your problem. For some reason, your network driver
couldnt find the PHY ... Maybe there is something changed
between 2.6.19-rc5 and 2.6.27.
> IP-Config: Failed to open eth0
> IP-Config: Failed to open eth1
> IP-Config: No network devices available.
and so, there is no network device ...
I have no 85xx board, but maybe following commit is something
for you:
gianfar: Convert gianfar to an of_platform_driver
author Andy Fleming <afleming@freescale.com>
Tue, 16 Dec 2008 23:29:15 +0000 (15:29 -0800)
committer David S. Miller <davem@davemloft.net>
Tue, 16 Dec 2008 23:29:15 +0000 (15:29 -0800)
commit b31a1d8b41513b96e9c7ec2f68c5734cef0b26a4
tree f8643c2fd1b137dd6c00bcd385ad36adfca4f540 tree | snapshot
parent 257d938a0c17838c740eb68f0005b041444ac2c2 commit | diff
gianfar: Convert gianfar to an of_platform_driver
Does the same for the accompanying MDIO driver, and then modifies the TBI
configuration method. The old way used fields in einfo, which no longer
exists. The new way is to create an MDIO device-tree node for each instance
of gianfar, and create a tbi-handle property to associate ethernet controllers
with the TBI PHYs they are connected to.
Signed-off-by: Andy Fleming <afleming@freescale.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
----------------------------------------------------------------------
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next parent reply other threads:[~2009-01-22 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1613.1232571316.4534.linuxppc-dev@ozlabs.org>
2009-01-22 9:17 ` Heiko Schocher [this message]
2009-01-22 12:06 ` eth0: Could not attach to PHY shreeram
2009-01-22 14:37 ` wael showair
2009-01-22 17:45 ` Haiying Wang
2009-01-22 18:00 ` Scott Wood
2009-01-23 8:48 ` Ratheesh
2009-01-21 18:37 wael showair
2009-01-22 14:34 ` Grant Likely
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=49783993.4090408@denx.de \
--to=hs@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=showair2003@yahoo.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 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).