From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Subject: Re: OMAP baseline test results for v3.7-rc1 Date: Sun, 21 Oct 2012 09:35:51 +0200 Message-ID: <20121021073551.GA4735@netboy.at.omicron.at> References: <20121020141136.GA6433@netboy.at.omicron.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:33594 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751667Ab2JUHgH (ORCPT ); Sun, 21 Oct 2012 03:36:07 -0400 Received: by mail-we0-f174.google.com with SMTP id t9so916026wey.19 for ; Sun, 21 Oct 2012 00:36:05 -0700 (PDT) Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org On Sat, Oct 20, 2012 at 04:27:19PM +0000, Paul Walmsley wrote: > Here's the console log from the boot test here: > > http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/20121017205513/boot/am335xbone/am335xbone_log.txt > > And here's the kernel config and uImage+DTB from the boot test here: > > http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/20121017205513/build/am33xx_only/ > > In terms of differences from your setup, looks like we have different > X-Loader and u-boot; it wouldn't surprise me if we have different kernel > configs too. Paul, You are using an obsolete u-boot and the "legacy" appended dtb method. It was my understanding that that way is just a temporary hack in case the boot loader does not support dtb. Now that u-boot has the proper support, using the dtb method is the "offical" boot method, AFAICT. At least, that is what people are saying on the arm list. So I think that if you want to test whether a particular board is booting correctly, it is more useful to try the offical method. People keep saying, the beaglebone works fine with v3.7-rc1, but it isn't true. Now v3.7-rc2 is out, and the gpmc issue still has not been fixed, and no one is doing anything about it either. When I read your report, it gave me a much rosier picture than is actually the case WRT the beaglebone. Thanks, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 From: richardcochran@gmail.com (Richard Cochran) Date: Sun, 21 Oct 2012 09:35:51 +0200 Subject: OMAP baseline test results for v3.7-rc1 In-Reply-To: References: <20121020141136.GA6433@netboy.at.omicron.at> Message-ID: <20121021073551.GA4735@netboy.at.omicron.at> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sat, Oct 20, 2012 at 04:27:19PM +0000, Paul Walmsley wrote: > Here's the console log from the boot test here: > > http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/20121017205513/boot/am335xbone/am335xbone_log.txt > > And here's the kernel config and uImage+DTB from the boot test here: > > http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/20121017205513/build/am33xx_only/ > > In terms of differences from your setup, looks like we have different > X-Loader and u-boot; it wouldn't surprise me if we have different kernel > configs too. Paul, You are using an obsolete u-boot and the "legacy" appended dtb method. It was my understanding that that way is just a temporary hack in case the boot loader does not support dtb. Now that u-boot has the proper support, using the dtb method is the "offical" boot method, AFAICT. At least, that is what people are saying on the arm list. So I think that if you want to test whether a particular board is booting correctly, it is more useful to try the offical method. People keep saying, the beaglebone works fine with v3.7-rc1, but it isn't true. Now v3.7-rc2 is out, and the gpmc issue still has not been fixed, and no one is doing anything about it either. When I read your report, it gave me a much rosier picture than is actually the case WRT the beaglebone. Thanks, Richard