From: Timur Tabi <timur@freescale.com>
To: Andre Schwarz <andre.schwarz@matrix-vision.de>
Cc: linuxppc-dev@ozlabs.org, afleming@freescale.com, netdev@vger.kernel.org
Subject: Re: "eth1: Could not attach to PHY" on MPC8349e-MITX
Date: Thu, 04 Dec 2008 11:47:26 -0600 [thread overview]
Message-ID: <493817AE.1070303@freescale.com> (raw)
In-Reply-To: <49381662.2020302@matrix-vision.de>
Andre Schwarz wrote:
> Timur,
>
> is it possible that the PHY adress doesn't match the one specified in
> the dts ?
What part of the DTS contains the PHY address? I have this:
mdio@24520 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,gianfar-mdio";
reg = <0x24520 0x20>;
/* Vitesse 8201 */
phy1c: ethernet-phy@1c {
interrupt-parent = <&ipic>;
interrupts = <18 0x8>;
reg = <0x1c>;
device_type = "ethernet-phy";
};
};
enet1: ethernet@25000 {
cell-index = <1>;
device_type = "network";
model = "TSEC";
compatible = "gianfar";
reg = <0x25000 0x1000>;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = <35 0x8 36 0x8 37 0x8>;
phy-connection-type = "mii";
interrupt-parent = <&ipic>;
/* Vitesse 7385 isn't on the MDIO bus */
fixed-link = <1 1 1000 0 0>;
linux,network-index = <1>;
};
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Andre Schwarz <andre.schwarz@matrix-vision.de>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org, afleming@freescale.com
Subject: Re: "eth1: Could not attach to PHY" on MPC8349e-MITX
Date: Thu, 04 Dec 2008 11:47:26 -0600 [thread overview]
Message-ID: <493817AE.1070303@freescale.com> (raw)
In-Reply-To: <49381662.2020302@matrix-vision.de>
Andre Schwarz wrote:
> Timur,
>
> is it possible that the PHY adress doesn't match the one specified in
> the dts ?
What part of the DTS contains the PHY address? I have this:
mdio@24520 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,gianfar-mdio";
reg = <0x24520 0x20>;
/* Vitesse 8201 */
phy1c: ethernet-phy@1c {
interrupt-parent = <&ipic>;
interrupts = <18 0x8>;
reg = <0x1c>;
device_type = "ethernet-phy";
};
};
enet1: ethernet@25000 {
cell-index = <1>;
device_type = "network";
model = "TSEC";
compatible = "gianfar";
reg = <0x25000 0x1000>;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = <35 0x8 36 0x8 37 0x8>;
phy-connection-type = "mii";
interrupt-parent = <&ipic>;
/* Vitesse 7385 isn't on the MDIO bus */
fixed-link = <1 1 1000 0 0>;
linux,network-index = <1>;
};
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-12-04 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 17:15 "eth1: Could not attach to PHY" on MPC8349e-MITX Timur Tabi
2008-12-04 17:41 ` Andre Schwarz
2008-12-04 17:47 ` Timur Tabi [this message]
2008-12-04 17:47 ` Timur Tabi
2008-12-04 17:56 ` Anton Vorontsov
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 17:52 ` Anton Vorontsov
2008-12-04 19:18 ` Timur Tabi
2008-12-04 19:18 ` Timur Tabi
2008-12-05 0:48 ` Kumar Gala
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=493817AE.1070303@freescale.com \
--to=timur@freescale.com \
--cc=afleming@freescale.com \
--cc=andre.schwarz@matrix-vision.de \
--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 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.