From: "Timur Tabi" <timur@freescale.com>
To: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org, afleming@freescale.com
Subject: "eth1: Could not attach to PHY" on MPC8349e-MITX
Date: Thu, 4 Dec 2008 11:15:32 -0600 [thread overview]
Message-ID: <ed82fe3e0812040915i696e99bep75a37b0e38154415@mail.gmail.com> (raw)
The Freescale MPC8349e-MITX reference board has two TSECs, the second
of which (eth1) is attached to a Vitesse 7385 5-port switch.
Using the latest U-Boot, Kernel, and device tree, I cannot bring up
eth1. When I try, I get this message:
[root@tintin root]# ifconfig eth1 up
0:01 not found
eth1: Could not attach to PHY
SIOCSIFFLAGS: No such device
Unfortunately, I don't even know what this means.
I believe my network configuration is correct. Here's what ifconfig
says about eth1:
eth1 Link encap:Ethernet HWaddr 00:E0:0C:00:8C:02
inet addr:192.168.2.141 Bcast:192.168.255.255 Mask:255.255.0.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0x4000
eth1 does work in U-boot, so I know it can be made to work (and I know
the 7385's firmware is uploaded), I just don't know what needs to be
done in Linux.
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2008-12-04 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 17:15 Timur Tabi [this message]
2008-12-04 17:41 ` "eth1: Could not attach to PHY" on MPC8349e-MITX Andre Schwarz
2008-12-04 17:47 ` Timur Tabi
2008-12-04 17:56 ` Anton Vorontsov
2008-12-04 17:56 ` Andre Schwarz
2008-12-04 17:52 ` [PATCH] powerpc/83xx: Enable FIXED_PHY in mpc834x_itx and mpc83xx defconfigs Anton Vorontsov
2008-12-04 19:18 ` Timur Tabi
2008-12-05 0:48 ` Kumar Gala
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=ed82fe3e0812040915i696e99bep75a37b0e38154415@mail.gmail.com \
--to=timur@freescale.com \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).