From: Peter Korsgaard <jacmet@sunsite.dk>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: Paul Walmsley <paul@pwsan.com>, 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>,
"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 10:40:46 +0100 [thread overview]
Message-ID: <87ham95zdt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1358846666.3996.3.camel@coredoba.hi.pengutronix.de> ("Jan Lübbe"'s message of "Tue, 22 Jan 2013 10:24:26 +0100")
>>>>> "Jan" == Jan Lübbe <jlu@pengutronix.de> writes:
Jan> On Tue, 2013-01-22 at 02:24 +0000, Paul Walmsley wrote:
>> 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.
Jan> Just a guess, but there can be problems when the appended DTB
Jan> crosses an 1MB boundary. See this mail for details and a patch:
Jan> http://www.spinics.net/lists/arm-kernel/msg216898.html
True, but that doesn't seem to be the case here:
ls -la arch/arm/boot/uImage
-rw-r--r-- 1 peko peko 3945127 Jan 22 09:26 arch/arm/boot/uImage
E.G. far from the 1MB boundary.
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-01-22 9:40 UTC|newest]
Thread overview: 32+ 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-21 16:32 ` Mark Jackson
2013-01-21 16:45 ` Nishanth Menon
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:34 ` Richard Cochran
2013-01-21 20:36 ` Peter Korsgaard
2013-01-22 2:24 ` Paul Walmsley
2013-01-22 8:55 ` Peter Korsgaard
2013-01-22 13:02 ` Bedia, Vaibhav
2013-01-22 9:24 ` Jan Lübbe
2013-01-22 9:40 ` Peter Korsgaard [this message]
2013-01-22 9:52 ` Russell King - ARM Linux
2013-01-22 12:19 ` Peter Korsgaard
2013-01-25 8:23 ` Paul Walmsley
2013-01-22 10:15 ` Mark Jackson
2013-01-22 12:21 ` Peter Korsgaard
2013-01-22 13:45 ` Mark Jackson
2013-01-22 13:32 ` Bedia, Vaibhav
2013-01-22 13:39 ` Mark Jackson
2013-01-22 18:23 ` Tony Lindgren
2013-01-23 10:18 ` Mark Jackson
2013-01-23 14:32 ` Bedia, Vaibhav
2013-01-25 16:59 ` Tony Lindgren
2013-01-28 12:23 ` Bedia, Vaibhav
2013-01-24 12:49 ` Bedia, Vaibhav
2013-01-25 8:42 ` Paul Walmsley
2013-02-06 22:00 ` Paul Walmsley
2013-02-06 22:20 ` Paul Walmsley
2013-02-07 14:42 ` Bedia, Vaibhav
[not found] ` <49ca66a84bb245ca9cfe4fd044c4d6f6@DFLE72.ent.ti.com>
2013-01-21 17:10 ` Matt Porter
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=87ham95zdt.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=hvaibhav@ti.com \
--cc=jlu@pengutronix.de \
--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=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox