Commit c7a7a5b9 authored by Wolfgang Denk's avatar Wolfgang Denk Committed by Kumar Gala

powerpc/mpc8272ads: fix device tree for 8 MB flash size

The current device tree for the MPC8272ADS assumes a mapping of 32 MB
of NOR flash at 0xFE00.0000, while there are actually only 8 MB on
the boards, mapped at 0xFF80.0000. When booting an uImage with such a
device tree, the kernel crashes because 0xFE00.0000 is not mapped.

Also introduce aliases for serial[01] and ethernet[01].
Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
Cc: Scott Wood <scottwood@freescale.com>
Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
parent 152d0182
......@@ -17,6 +17,13 @@ / {
#address-cells = <1>;
#size-cells = <1>;
aliases {
ethernet0 = &eth0;
ethernet1 = &eth1;
serial0 = &scc1;
serial1 = &scc4;
};
cpus {
#address-cells = <1>;
#size-cells = <0>;
......@@ -46,13 +53,13 @@ localbus@f0010100 {
#size-cells = <1>;
reg = <0xf0010100 0x40>;
ranges = <0x0 0x0 0xfe000000 0x2000000
ranges = <0x0 0x0 0xff800000 0x00800000
0x1 0x0 0xf4500000 0x8000
0x3 0x0 0xf8200000 0x8000>;
flash@0,0 {
compatible = "jedec-flash";
reg = <0x0 0x0 0x2000000>;
reg = <0x0 0x0 0x00800000>;
bank-width = <4>;
device-width = <1>;
};
......@@ -144,7 +151,7 @@ brg@119f0 {
reg = <0x119f0 0x10 0x115f0 0x10>;
};
serial@11a00 {
scc1: serial@11a00 {
device_type = "serial";
compatible = "fsl,mpc8272-scc-uart",
"fsl,cpm2-scc-uart";
......@@ -155,7 +162,7 @@ serial@11a00 {
fsl,cpm-command = <0x800000>;
};
serial@11a60 {
scc4: serial@11a60 {
device_type = "serial";
compatible = "fsl,mpc8272-scc-uart",
"fsl,cpm2-scc-uart";
......@@ -192,7 +199,7 @@ PHY1: ethernet-phy@1 {
};
};
ethernet@11300 {
eth0: ethernet@11300 {
device_type = "network";
compatible = "fsl,mpc8272-fcc-enet",
"fsl,cpm2-fcc-enet";
......@@ -205,7 +212,7 @@ ethernet@11300 {
fsl,cpm-command = <0x12000300>;
};
ethernet@11320 {
eth1: ethernet@11320 {
device_type = "network";
compatible = "fsl,mpc8272-fcc-enet",
"fsl,cpm2-fcc-enet";
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment