linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.8-rc4
Date: Tue, 22 Jan 2013 09:52:18 +0000	[thread overview]
Message-ID: <20130122095218.GD2637@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <87ham95zdt.fsf@dell.be.48ers.dk>

On Tue, Jan 22, 2013 at 10:40:46AM +0100, Peter Korsgaard wrote:
> >>>>> "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.

Don't rely on that.  Remember, if the compressed image occupies the same
location as the decompressed kernel, the decompressor will copy the data
to a different location in RAM first - I think at RAM offset + 32K +
decompressed kernel size.

So yes, please try the patch in the link above.

  reply	other threads:[~2013-01-22  9:52 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
2013-01-22  9:52                 ` Russell King - ARM Linux [this message]
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=20130122095218.GD2637@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).