Re: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on core1 of AMP boot issue
On 07/10/2012 09:07 PM, Jia Hongtao-B38951 wrote: > > >> -Original Message- >> From: Wood Scott-B07421 >> Sent: Wednesday, July 11, 2012 2:15 AM >> To: Jia Hongtao-B38951 >> Cc: linuxppc-dev@lists.ozlabs.org; ga...@kernel.crashing.org >> Subject: Re: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on >> core1 of AMP boot issue >> >> On 07/10/2012 01:08 AM, Jia Hongtao wrote: >>> The issue log on core1 is: >>> root@mpc8572ds:~# ifconfig eth0 10.192.208.244 >>> net eth0: could not attach to PHY >>> SIOCSIFFLAGS: No such device >>> >>> To attach PHY node mdio@24520 should not be disabled in dts of core1. >>> Because all PHYs are controlled through this node as follows: >> >> So you grant it to both partitions? How do you deal with synchronization? >> >> -Scott > > PHY nodes are only used by ethernet. Each ethernet is used by only one > partition > (disabled in the other partition). So I think there is no synchronization > issue. I mean for accessing the MDIO bus. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on core1 of AMP boot issue
> -Original Message- > From: Wood Scott-B07421 > Sent: Wednesday, July 11, 2012 2:15 AM > To: Jia Hongtao-B38951 > Cc: linuxppc-dev@lists.ozlabs.org; ga...@kernel.crashing.org > Subject: Re: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on > core1 of AMP boot issue > > On 07/10/2012 01:08 AM, Jia Hongtao wrote: > > The issue log on core1 is: > > root@mpc8572ds:~# ifconfig eth0 10.192.208.244 > > net eth0: could not attach to PHY > > SIOCSIFFLAGS: No such device > > > > To attach PHY node mdio@24520 should not be disabled in dts of core1. > > Because all PHYs are controlled through this node as follows: > > So you grant it to both partitions? How do you deal with synchronization? > > -Scott PHY nodes are only used by ethernet. Each ethernet is used by only one partition (disabled in the other partition). So I think there is no synchronization issue. Thanks. -Jia Hongtao. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on core1 of AMP boot issue
On 07/10/2012 01:08 AM, Jia Hongtao wrote: > The issue log on core1 is: > root@mpc8572ds:~# ifconfig eth0 10.192.208.244 > net eth0: could not attach to PHY > SIOCSIFFLAGS: No such device > > To attach PHY node mdio@24520 should not be disabled in dts of core1. > Because all PHYs are controlled through this node as follows: So you grant it to both partitions? How do you deal with synchronization? -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on core1 of AMP boot issue
On Jul 10, 2012, at 1:08 AM, Jia Hongtao wrote: > The issue log on core1 is: > root@mpc8572ds:~# ifconfig eth0 10.192.208.244 > net eth0: could not attach to PHY > SIOCSIFFLAGS: No such device > > To attach PHY node mdio@24520 should not be disabled in dts of core1. > Because all PHYs are controlled through this node as follows: > > mdio@24520 { > phy0: ethernet-phy@0 { > interrupts = <10 1 0 0>; > reg = <0x0>; > }; > phy1: ethernet-phy@1 { > interrupts = <10 1 0 0>; > reg = <0x1>; > }; > phy2: ethernet-phy@2 { > interrupts = <10 1 0 0>; > reg = <0x2>; > }; > phy3: ethernet-phy@3 { > interrupts = <10 1 0 0>; > reg = <0x3>; > }; > > tbi0: tbi-phy@11 { > reg = <0x11>; > device_type = "tbi-phy"; > }; > }; > > Signed-off-by: Li Yang > Signed-off-by: Jia Hongtao > --- > arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts |3 --- > 1 files changed, 0 insertions(+), 3 deletions(-) applied to next - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
[PATCH 1/2] powerpc/mpc8572ds: Fix eTSEC is not available on core1 of AMP boot issue
The issue log on core1 is: root@mpc8572ds:~# ifconfig eth0 10.192.208.244 net eth0: could not attach to PHY SIOCSIFFLAGS: No such device To attach PHY node mdio@24520 should not be disabled in dts of core1. Because all PHYs are controlled through this node as follows: mdio@24520 { phy0: ethernet-phy@0 { interrupts = <10 1 0 0>; reg = <0x0>; }; phy1: ethernet-phy@1 { interrupts = <10 1 0 0>; reg = <0x1>; }; phy2: ethernet-phy@2 { interrupts = <10 1 0 0>; reg = <0x2>; }; phy3: ethernet-phy@3 { interrupts = <10 1 0 0>; reg = <0x3>; }; tbi0: tbi-phy@11 { reg = <0x11>; device_type = "tbi-phy"; }; }; Signed-off-by: Li Yang Signed-off-by: Jia Hongtao --- arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts |3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts b/arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts index d6a8faf..1932396 100644 --- a/arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts +++ b/arch/powerpc/boot/dts/mpc8572ds_camp_core1.dts @@ -67,9 +67,6 @@ ethernet@24000 { status = "disabled"; }; - mdio@24520 { - status = "disabled"; - }; ptp_clock@24e00 { status = "disabled"; }; -- 1.7.5.1 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev