lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <493817AE.1070303@freescale.com>
Date:	Thu, 04 Dec 2008 11:47:26 -0600
From:	Timur Tabi <timur@...escale.com>
To:	Andre Schwarz <andre.schwarz@...rix-vision.de>
CC:	linuxppc-dev@...abs.org, netdev@...r.kernel.org,
	afleming@...escale.com
Subject: Re: "eth1: Could not attach to PHY" on MPC8349e-MITX

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@...20 {
		#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@...00 {
		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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ