All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: Matt Porter <mporter@ti.com>,
	Richard Cochran <richardcochran@gmail.com>, "Menon\\,
	Nishanth" <nm@ti.com>, Mark Jackson <mpfj-list@mimc.co.uk>,
	"Hiremath\\, Vaibhav" <hvaibhav@ti.com>,
	Vaibhav Bedia <vaibhav.bedia@ti.com>,
	Peter Korsgaard <jacmet@sunsite.dk>
Cc: "linux-omap\\@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel\\@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: OMAP baseline test results for v3.8-rc4
Date: Tue, 22 Jan 2013 02:24:44 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.1301220213390.25789@utopia.booyaka.com> (raw)
In-Reply-To: <87boci9str.fsf@dell.be.48ers.dk>


Hi guys,

Regarding the AM33xx test failures with appended DTBs, it would be very 
helpful if especially the TI people could try reproducing the problem.
Otherwise it's going to cause problems with merging any new AM33xx 
patches, since I won't be able to test them without additional work.  
Plus, this is something that used to work up until d01e4afd, so something 
isn't right.

You'll need to use the bootloader that TI originally shipped with the 
BeagleBones:

U-Boot 2011.09-00009-gcf6e04d (Mar 08 2012 - 17:15:43)

This is because many folks don't replace their bootloader.  I do plan to 
add a test with a recent version of u-boot, but the kernel should not be 
dependent on the bootloader in any way to work correctly.  If it is, then 
we need to document what u-boot version the kernel started to work with.

The Kconfig that I use is here:

http://www.pwsan.com/omap/testlogs/test_v3.8-rc4/20130120122039/build/am33xx_only/am33xx_only

It's possible that there's something wrong with the Kconfig.  It's 
basically just omap2plus_defconfig, but with all OMAP support for 
non-AM33xx turned off, and with the appended DTB and ATAG compatibility 
options turned on.

Let's try to do this ASAP.  That way, if it's some bootloader dependency 
or bug in the kernel, some fix can be merged during the v3.8-rc series, 
which is rapidly drawing to a close.


- Paul

WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.8-rc4
Date: Tue, 22 Jan 2013 02:24:44 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.00.1301220213390.25789@utopia.booyaka.com> (raw)
In-Reply-To: <87boci9str.fsf@dell.be.48ers.dk>


Hi guys,

Regarding the AM33xx test failures with appended DTBs, it would be very 
helpful if especially the TI people could try reproducing the problem.
Otherwise it's going to cause problems with merging any new AM33xx 
patches, since I won't be able to test them without additional work.  
Plus, this is something that used to work up until d01e4afd, so something 
isn't right.

You'll need to use the bootloader that TI originally shipped with the 
BeagleBones:

U-Boot 2011.09-00009-gcf6e04d (Mar 08 2012 - 17:15:43)

This is because many folks don't replace their bootloader.  I do plan to 
add a test with a recent version of u-boot, but the kernel should not be 
dependent on the bootloader in any way to work correctly.  If it is, then 
we need to document what u-boot version the kernel started to work with.

The Kconfig that I use is here:

http://www.pwsan.com/omap/testlogs/test_v3.8-rc4/20130120122039/build/am33xx_only/am33xx_only

It's possible that there's something wrong with the Kconfig.  It's 
basically just omap2plus_defconfig, but with all OMAP support for 
non-AM33xx turned off, and with the appended DTB and ATAG compatibility 
options turned on.

Let's try to do this ASAP.  That way, if it's some bootloader dependency 
or bug in the kernel, some fix can be merged during the v3.8-rc series, 
which is rapidly drawing to a close.


- Paul

  reply	other threads:[~2013-01-22  2:24 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20 21:38 OMAP baseline test results for v3.8-rc4 Paul Walmsley
2013-01-20 21:38 ` Paul Walmsley
2013-01-21 16:32 ` Mark Jackson
2013-01-21 16:32   ` Mark Jackson
2013-01-21 16:45   ` Nishanth Menon
2013-01-21 16:45     ` Nishanth Menon
2013-01-21 18:20     ` Richard Cochran
2013-01-21 18:20       ` Richard Cochran
     [not found]     ` <f36acfaf128c4844b8f696ea4440e253@DLEE74.ent.ti.com>
2013-01-21 18:24       ` Matt Porter
2013-01-21 18:24         ` Matt Porter
2013-01-21 18:34         ` Richard Cochran
2013-01-21 18:34           ` Richard Cochran
2013-01-21 20:36         ` Peter Korsgaard
2013-01-21 20:36           ` Peter Korsgaard
2013-01-22  2:24           ` Paul Walmsley [this message]
2013-01-22  2:24             ` Paul Walmsley
2013-01-22  8:55             ` Peter Korsgaard
2013-01-22  8:55               ` Peter Korsgaard
2013-01-22 13:02               ` Bedia, Vaibhav
2013-01-22 13:02                 ` Bedia, Vaibhav
2013-01-22  9:24             ` Jan Lübbe
2013-01-22  9:24               ` Jan Lübbe
2013-01-22  9:40               ` Peter Korsgaard
2013-01-22  9:40                 ` Peter Korsgaard
2013-01-22  9:52                 ` Russell King - ARM Linux
2013-01-22  9:52                   ` Russell King - ARM Linux
2013-01-22 12:19                   ` Peter Korsgaard
2013-01-22 12:19                     ` Peter Korsgaard
2013-01-25  8:23               ` Paul Walmsley
2013-01-25  8:23                 ` Paul Walmsley
2013-01-22 10:15             ` Mark Jackson
2013-01-22 10:15               ` Mark Jackson
2013-01-22 12:21               ` Peter Korsgaard
2013-01-22 12:21                 ` Peter Korsgaard
2013-01-22 13:45                 ` Mark Jackson
2013-01-22 13:45                   ` Mark Jackson
2013-01-22 13:32               ` Bedia, Vaibhav
2013-01-22 13:32                 ` Bedia, Vaibhav
2013-01-22 13:39                 ` Mark Jackson
2013-01-22 13:39                   ` Mark Jackson
2013-01-22 18:23                   ` Tony Lindgren
2013-01-22 18:23                     ` Tony Lindgren
2013-01-23 10:18                     ` Mark Jackson
2013-01-23 10:18                       ` Mark Jackson
2013-01-23 14:32                     ` Bedia, Vaibhav
2013-01-23 14:32                       ` Bedia, Vaibhav
2013-01-25 16:59                       ` Tony Lindgren
2013-01-25 16:59                         ` Tony Lindgren
2013-01-28 12:23                         ` Bedia, Vaibhav
2013-01-28 12:23                           ` Bedia, Vaibhav
2013-01-24 12:49             ` Bedia, Vaibhav
2013-01-24 12:49               ` Bedia, Vaibhav
2013-01-25  8:42               ` Paul Walmsley
2013-01-25  8:42                 ` Paul Walmsley
2013-02-06 22:00               ` Paul Walmsley
2013-02-06 22:00                 ` Paul Walmsley
2013-02-06 22:20                 ` Paul Walmsley
2013-02-06 22:20                   ` Paul Walmsley
2013-02-07 14:42                 ` Bedia, Vaibhav
2013-02-07 14:42                   ` Bedia, Vaibhav
     [not found] ` <49ca66a84bb245ca9cfe4fd044c4d6f6@DFLE72.ent.ti.com>
2013-01-21 17:10   ` Matt Porter
2013-01-21 17:10     ` Matt Porter
2013-01-21 20:36     ` Peter Korsgaard
2013-01-21 20:36       ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.00.1301220213390.25789@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=hvaibhav@ti.com \
    --cc=jacmet@sunsite.dk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mpfj-list@mimc.co.uk \
    --cc=mporter@ti.com \
    --cc=nm@ti.com \
    --cc=richardcochran@gmail.com \
    --cc=vaibhav.bedia@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.