From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sricharan R Subject: Re: [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c Date: Thu, 13 Jun 2013 15:42:23 +0530 Message-ID: <51B99B07.1050806@ti.com> References: <20130517191304.468.73487.stgit@localhost> <20130517191753.468.1734.stgit@localhost> <20130612163124.GD8164@atomide.com> <20130612171407.GM8164@atomide.com> <51B98F1E.1000006@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from arroyo.ext.ti.com ([192.94.94.40]:57622 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756164Ab3FMKMv (ORCPT ); Thu, 13 Jun 2013 06:12:51 -0400 In-Reply-To: <51B98F1E.1000006@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren Cc: Ming Lei , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org On Thursday 13 June 2013 02:51 PM, Sricharan R wrote: > Hi Tony, > On Wednesday 12 June 2013 10:44 PM, Tony Lindgren wrote: >> * Tony Lindgren [130612 09:37]: >>> * Ming Lei [130603 08:34]: >>>> Hi, >>>> >>>> On Sat, May 18, 2013 at 3:17 AM, Tony Lindgren wrote: >>>>> We can now boot with device tree. If you don't want to update u-boot, >>>>> you can boot with appended DTB with the following instructions: >>>>> >>>>> 1. Make sure you have the appended DTB support in .config >>>>> >>>>> CONFIG_ARM_APPENDED_DTB=y >>>>> CONFIG_ARM_ATAG_DTB_COMPAT=y >>>>> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y >>>>> >>>>> 2. Build the zImage >>>>> >>>>> $ ARCH=arm CROSS_COMPILE=... make zImage >>>>> >>>>> 3. Build the device tree blobs >>>>> >>>>> $ ARCH=arm CROSS_COMPILE=... make dtbs >>>>> >>>>> 4. Append the correct panda dtb to zImage >>>>> >>>>> Depending on your hardware it's omap4-panda.dtb, omap4-panda-a4.dtb >>>>> or omap4-panda-es.dtb. >>>>> >>>>> $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap4-panda-es.dtb > /tmp/appended >>>>> >>>>> 5. Use mkimage to produce the appended device tree uImage >>>>> >>>>> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \ >>>>> -n "Linux" -d /tmp/appended /tmp/uImage >>>> I followed the above steps and tried devicetree on Pandaboard against >>>> 3.10.0-rc3-next-20130528, and the board will hang during boot, but works >>>> well with legacy mode. >>>> >>>> Hardware: Pandaboard A1 >>>> dtb: omap4-panda.dtb >>>> >>>> See 'dmesg' on below link: >>>> >>>> http://kernel.ubuntu.com/~ming/up/panda-dts.dmesg >>>> >>> Hmm looks like it boots to init. Maybe add initcall_debug to the cmdline in >>> case there's some late_initcall that causes the issue. It's probably some >>> trivial issue causing it. >> Sricharan, maybe give this a quick try if you have the original pandaboard? >> I only have pandaboard es. >> >> Regards, >> >> Tony > > I tried your cleanup branch omap-for-v3.11/cleanup on panda board and it booted > to prompt fine. > Hardware: Pandaboard A1 dtb: omap4-panda.dtb > > git pull on linux-next branch was not working though. > Ok, tested in linux-next as well and it booted fine with DTB. HW: OMAP4430ES2.1 PANDA A1 version DTB: OMAP4-PANDA.DTB Booted with ramdisk and mmc FS commit c04efed734409f5a44715b54a6ca1b54b0ccf215 Author: Stephen Rothwell Date: Fri Jun 7 16:40:02 2013 +1000 Add linux-next specific files for 20130607 Regards, Sricharan From mboxrd@z Thu Jan 1 00:00:00 1970 From: r.sricharan@ti.com (Sricharan R) Date: Thu, 13 Jun 2013 15:42:23 +0530 Subject: [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c In-Reply-To: <51B98F1E.1000006@ti.com> References: <20130517191304.468.73487.stgit@localhost> <20130517191753.468.1734.stgit@localhost> <20130612163124.GD8164@atomide.com> <20130612171407.GM8164@atomide.com> <51B98F1E.1000006@ti.com> Message-ID: <51B99B07.1050806@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thursday 13 June 2013 02:51 PM, Sricharan R wrote: > Hi Tony, > On Wednesday 12 June 2013 10:44 PM, Tony Lindgren wrote: >> * Tony Lindgren [130612 09:37]: >>> * Ming Lei [130603 08:34]: >>>> Hi, >>>> >>>> On Sat, May 18, 2013 at 3:17 AM, Tony Lindgren wrote: >>>>> We can now boot with device tree. If you don't want to update u-boot, >>>>> you can boot with appended DTB with the following instructions: >>>>> >>>>> 1. Make sure you have the appended DTB support in .config >>>>> >>>>> CONFIG_ARM_APPENDED_DTB=y >>>>> CONFIG_ARM_ATAG_DTB_COMPAT=y >>>>> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y >>>>> >>>>> 2. Build the zImage >>>>> >>>>> $ ARCH=arm CROSS_COMPILE=... make zImage >>>>> >>>>> 3. Build the device tree blobs >>>>> >>>>> $ ARCH=arm CROSS_COMPILE=... make dtbs >>>>> >>>>> 4. Append the correct panda dtb to zImage >>>>> >>>>> Depending on your hardware it's omap4-panda.dtb, omap4-panda-a4.dtb >>>>> or omap4-panda-es.dtb. >>>>> >>>>> $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap4-panda-es.dtb > /tmp/appended >>>>> >>>>> 5. Use mkimage to produce the appended device tree uImage >>>>> >>>>> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \ >>>>> -n "Linux" -d /tmp/appended /tmp/uImage >>>> I followed the above steps and tried devicetree on Pandaboard against >>>> 3.10.0-rc3-next-20130528, and the board will hang during boot, but works >>>> well with legacy mode. >>>> >>>> Hardware: Pandaboard A1 >>>> dtb: omap4-panda.dtb >>>> >>>> See 'dmesg' on below link: >>>> >>>> http://kernel.ubuntu.com/~ming/up/panda-dts.dmesg >>>> >>> Hmm looks like it boots to init. Maybe add initcall_debug to the cmdline in >>> case there's some late_initcall that causes the issue. It's probably some >>> trivial issue causing it. >> Sricharan, maybe give this a quick try if you have the original pandaboard? >> I only have pandaboard es. >> >> Regards, >> >> Tony > > I tried your cleanup branch omap-for-v3.11/cleanup on panda board and it booted > to prompt fine. > Hardware: Pandaboard A1 dtb: omap4-panda.dtb > > git pull on linux-next branch was not working though. > Ok, tested in linux-next as well and it booted fine with DTB. HW: OMAP4430ES2.1 PANDA A1 version DTB: OMAP4-PANDA.DTB Booted with ramdisk and mmc FS commit c04efed734409f5a44715b54a6ca1b54b0ccf215 Author: Stephen Rothwell Date: Fri Jun 7 16:40:02 2013 +1000 Add linux-next specific files for 20130607 Regards, Sricharan