From: Prasanna Khanapur <pskhanapur@googlemail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Regarding P2020 in AMP mode
Date: Sat, 7 May 2011 14:20:46 +0200 [thread overview]
Message-ID: <BANLkTik7tZSJ9-OPDbQEPJDHpZ13wMmo_Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
Hi,
I'm running P2020 in AMP mode, each core running its linux os.
Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are working
fine.
I'm facing problems with Ethernet interface(@24000) assigned to Core1, its
not working.
I'm using dts file which were added by :
http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-September/075594.html
Looks either there is some mistake in the dts file or my understanding is
wrong.
MDIO @24000 is defined in core0 dts file though the Ethernet is assigned to
Core 1.
DTS files :
http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core0.dts
http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core1.dts
mdio@24520 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,gianfar-mdio";
reg = <0x24520 0x20>;
phy0: ethernet-phy@0 {
interrupt-parent = <&mpic>;
interrupts = <3 1>;
reg = <0x0>;
};
phy1: ethernet-phy@1 {
interrupt-parent = <&mpic>;
interrupts = <3 1>;
reg = <0x1>;
};
};
Also, MDIO for 25520 has wrong register value:
mdio@25520 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,gianfar-tbi";
reg = <0x26520 0x20>;
tbi0: tbi-phy@11 {
reg = <0x11>;
device_type = "tbi-phy";
};
};
Please correct me if I'm wrong. Has freescale released a working dts files
for P2020 in AMP mode ? as this seems to be not working.
Best Regards
Prasanna Khanapur.
[-- Attachment #2: Type: text/html, Size: 3019 bytes --]
next reply other threads:[~2011-05-07 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 12:20 Prasanna Khanapur [this message]
2011-05-09 20:22 ` Regarding P2020 in AMP mode Hollis Blanchard
2011-05-10 7:50 ` Aggrwal Poonam-B10812
2011-05-11 11:23 ` Prasanna Khanapur
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=BANLkTik7tZSJ9-OPDbQEPJDHpZ13wMmo_Q@mail.gmail.com \
--to=pskhanapur@googlemail.com \
--cc=linuxppc-dev@lists.ozlabs.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).