Based on the original omap4-panda.dts file from Manju. http://www.spinics.net/lists/linux-omap/msg55836.html
Add memory information and a default bootargs to allow a boot from RAMDISK. Add missing header. Include the common omap4.dtsi. Add a "ti,omap4" compatible value for OMAP4 based boards. Signed-off-by: Benoit Cousson <[email protected]> Cc: Grant Likely <[email protected]> Cc: G, Manjunath Kondaiah <[email protected]> --- arch/arm/boot/dts/omap4-panda.dts | 28 +++++++++++++++++++++++----- 1 files changed, 23 insertions(+), 5 deletions(-) diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts index 58909e9..c702657 100644 --- a/arch/arm/boot/dts/omap4-panda.dts +++ b/arch/arm/boot/dts/omap4-panda.dts @@ -1,11 +1,29 @@ +/* + * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/ + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ /dts-v1/; -/memreserve/ 0x9D000000 0x03000000; /* Frame buffer */ -/memreserve/ 0xB0000000 0x10000000; /* Top 256MB is unaccessable */ - -/include/ "skeleton.dtsi" +/include/ "omap4.dtsi" / { model = "TI OMAP4 PandaBoard"; - compatible = "ti,omap4-panda", "ti,omap4430"; + compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4"; + + /* + * Since the initial device tree board file does not create any + * devices (MMC, network...), the only way to boot is to provide a + * ramdisk. + */ + chosen { + bootargs = "root=/dev/ram0 rw console=ttyO2,115200n8 initrd=0x81600000,20M ramdisk_size=20480 no_console_suspend debug"; + }; + + memory { + device_type = "memory"; + reg = <0x80000000 0x40000000>; /* 1 GB */ + }; }; -- 1.7.0.4 _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
