From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Porter Subject: Re: OMAP baseline test results for v3.7-rc2 Date: Mon, 22 Oct 2012 21:53:46 -0400 Message-ID: <20121023015346.GB1855@beef> References: <50857444.9080308@ti.com> <50859505.5010306@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-ie0-f174.google.com ([209.85.223.174]:43930 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756492Ab2JWBxu (ORCPT ); Mon, 22 Oct 2012 21:53:50 -0400 Received: by mail-ie0-f174.google.com with SMTP id k13so4635646iea.19 for ; Mon, 22 Oct 2012 18:53:49 -0700 (PDT) Content-Disposition: inline In-Reply-To: <50859505.5010306@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Jon Hunter Cc: Paul Walmsley , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Mon, Oct 22, 2012 at 01:48:37PM -0500, Jon Hunter wrote: > > On 10/22/2012 01:35 PM, Paul Walmsley wrote: > > (including the lists in my reply this time, oops; also adding some more > > detail) > > > > On Mon, 22 Oct 2012, Jon Hunter wrote: > > > >> On 10/20/2012 04:26 PM, Paul Walmsley wrote: > >> > >>> Failing tests: fixed by posted patches > >>> -------------------------------------- > >>> > >>> Boot tests: > >>> > >>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot > >>> - due to a GPMC bug > >>> - Apparently fixed by http://www.spinics.net/lists/arm-kernel/msg200787.html > >> > >> This is now addressed and I have verified it is booting on v3.7-rc2. The > >> following patch address this boot problem ... > >> > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8119024ef7363591fd958ec89ebfaee7c18209e3 > > > > Great, thanks, will update the README. Did you also enable > > CONFIG_ARM_APPENDED_DTB and CONFIG_ARM_ATAG_DTB_COMPAT, or were you able > > to pass the DTB from the bootloader? > > Actually, I built u-boot release 2012.10 for the am335x-evm and that > worked for the bone board too. So that is what I used. I have not > checked with Vaibhav and team if that is what they are using. So with > this u-boot I just passed the dtb to the kernel and did not append. I've mentioned this a few times in various threads...no need to use appended DTB on a current U-Boot. Some of us are indeed booting this way with the DTB properly passed separately from the bootloader and chosen filled out by the bootloader. And yes, am335x_evm_config applies to all AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all that is used to determine what board is present so a single MLO/u-boot.img can be used. BTW, if you pick up an RS-232 cape, you can avoid using the FTDI->UART0 connection for console and switch to any UART brought out on the Bone connectors. This is useful for those using a power controller and console server for local automated testing. -Matt From mboxrd@z Thu Jan 1 00:00:00 1970 From: mporter@ti.com (Matt Porter) Date: Mon, 22 Oct 2012 21:53:46 -0400 Subject: OMAP baseline test results for v3.7-rc2 In-Reply-To: <50859505.5010306@ti.com> References: <50857444.9080308@ti.com> <50859505.5010306@ti.com> Message-ID: <20121023015346.GB1855@beef> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 22, 2012 at 01:48:37PM -0500, Jon Hunter wrote: > > On 10/22/2012 01:35 PM, Paul Walmsley wrote: > > (including the lists in my reply this time, oops; also adding some more > > detail) > > > > On Mon, 22 Oct 2012, Jon Hunter wrote: > > > >> On 10/20/2012 04:26 PM, Paul Walmsley wrote: > >> > >>> Failing tests: fixed by posted patches > >>> -------------------------------------- > >>> > >>> Boot tests: > >>> > >>> * AM335x Beaglebone: omap2plus_defconfig kernels don't boot > >>> - due to a GPMC bug > >>> - Apparently fixed by http://www.spinics.net/lists/arm-kernel/msg200787.html > >> > >> This is now addressed and I have verified it is booting on v3.7-rc2. The > >> following patch address this boot problem ... > >> > >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8119024ef7363591fd958ec89ebfaee7c18209e3 > > > > Great, thanks, will update the README. Did you also enable > > CONFIG_ARM_APPENDED_DTB and CONFIG_ARM_ATAG_DTB_COMPAT, or were you able > > to pass the DTB from the bootloader? > > Actually, I built u-boot release 2012.10 for the am335x-evm and that > worked for the bone board too. So that is what I used. I have not > checked with Vaibhav and team if that is what they are using. So with > this u-boot I just passed the dtb to the kernel and did not append. I've mentioned this a few times in various threads...no need to use appended DTB on a current U-Boot. Some of us are indeed booting this way with the DTB properly passed separately from the bootloader and chosen filled out by the bootloader. And yes, am335x_evm_config applies to all AM33xx TI EVMs and the BeagleBone board. There's an EEPROM onboard all that is used to determine what board is present so a single MLO/u-boot.img can be used. BTW, if you pick up an RS-232 cape, you can avoid using the FTDI->UART0 connection for console and switch to any UART brought out on the Bone connectors. This is useful for those using a power controller and console server for local automated testing. -Matt