Without device_type property set as memory for the node, the generated dtb can still work when it gets passed to kernel by u-boot, since u-boot will fix it up. But kernel will not boot due to that it fails to parse the memory node, when the dtb is appended to kernel image as it is.
The patch adds a property device_type="memory" for memory node to fix the problem.
Signed-off-by: Shawn Guo shawn.guo@linaro.org --- It applies on branch devicetree/test.
arch/arm/boot/dts/babbage.dts | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/babbage.dts b/arch/arm/boot/dts/babbage.dts index 8f9b47c..4805168 100644 --- a/arch/arm/boot/dts/babbage.dts +++ b/arch/arm/boot/dts/babbage.dts @@ -21,6 +21,7 @@ interrupt-parent = <&tzic>;
memory { + device_type = "memory"; reg = <0x90000000 0x20000000>; };
On 22 April 2011 01:25, Shawn Guo shawn.guo@linaro.org wrote:
Without device_type property set as memory for the node, the generated dtb can still work when it gets passed to kernel by u-boot, since u-boot will fix it up. But kernel will not boot due to that it fails to parse the memory node, when the dtb is appended to kernel image as it is.
I'm a little confused. The first part of the statement implies that the kernel will boot without the device_type property, but the second part of the statement says that the kernel won't boot.
The patch adds a property device_type="memory" for memory node to fix the problem.
Signed-off-by: Shawn Guo shawn.guo@linaro.org
It applies on branch devicetree/test.
arch/arm/boot/dts/babbage.dts | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/babbage.dts b/arch/arm/boot/dts/babbage.dts index 8f9b47c..4805168 100644 --- a/arch/arm/boot/dts/babbage.dts +++ b/arch/arm/boot/dts/babbage.dts @@ -21,6 +21,7 @@ interrupt-parent = <&tzic>;
memory {
- device_type = "memory";
reg = <0x90000000 0x20000000>; };
-- 1.7.4.1
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Sat, Apr 23, 2011 at 04:39:15PM -0500, Zach Pfeffer wrote:
On 22 April 2011 01:25, Shawn Guo shawn.guo@linaro.org wrote:
Without device_type property set as memory for the node, the generated dtb can still work when it gets passed to kernel by u-boot, since u-boot will fix it up. But kernel will not boot due to that it fails to parse the memory node, when the dtb is appended to kernel image as it is.
I'm a little confused. The first part of the statement implies that the kernel will boot without the device_type property, but the second part of the statement says that the kernel won't boot.
The second part is talking about using John Bonesio's patch to append dtb to zImage like: 'cat zImage babbage.dtb > zImage_w_dtb'.
Hi Grant,
Let me know if you prefer to get babbage.dts deprecated by merging it into mx51-babbage.dts.
On Fri, Apr 22, 2011 at 02:25:26PM +0800, Shawn Guo wrote:
Without device_type property set as memory for the node, the generated dtb can still work when it gets passed to kernel by u-boot, since u-boot will fix it up. But kernel will not boot due to that it fails to parse the memory node, when the dtb is appended to kernel image as it is.
The patch adds a property device_type="memory" for memory node to fix the problem.
Signed-off-by: Shawn Guo shawn.guo@linaro.org
It applies on branch devicetree/test.
arch/arm/boot/dts/babbage.dts | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/babbage.dts b/arch/arm/boot/dts/babbage.dts index 8f9b47c..4805168 100644 --- a/arch/arm/boot/dts/babbage.dts +++ b/arch/arm/boot/dts/babbage.dts @@ -21,6 +21,7 @@ interrupt-parent = <&tzic>; memory {
device_type = "memory";
Hi Grant, comments?
linaro-kernel@lists.linaro.org
-
Shawn Guo -
Shawn Guo -
Zach Pfeffer