From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 9c11135 breaks bootz
Date: Thu, 4 Feb 2016 12:41:27 -0500 [thread overview]
Message-ID: <20160204174127.GI25786@bill-the-cat> (raw)
In-Reply-To: <CAO8h3eEGQnLooe6+oeSdWjU_nTsgE54HgH8n2NKMgGVRk5BdmQ@mail.gmail.com>
On Tue, Feb 02, 2016 at 03:49:07PM +0100, Matthias Wei?er wrote:
> Hi
>
> 9c11135 image: fix getenv_bootm_size() function breaks the bootz
> command for me on a custom hardware (very similar to mx6sxsabresd but
> with only 256MB RAM). I don't have bootm_size or bootm_low defined.
>
> After reading zImage and dtb from serial flash I run
>
> => bootz 0x80800000 - 0x83000000
> Kernel image @ 0x80800000 [ 0x000000 - 0x1e5f48 ]
> ## Flattened Device Tree blob at 83000000
> Booting using the fdt blob at 0x83000000
> ERROR: Failed to allocate 0xb28a bytes below 0x10000000.
> device tree - allocation error
> FDT creation failed! hanging...### ERROR ### Please RESET the board ###
>
> I am totally unsure what the commit intents but subtracting the ram
> start address from its size doesn't make much sense to me.
>
> + return gd->bd->bi_dram[0].size - (tmp - gd->bd->bi_dram[0].start);
>
> Maybe someone can shed some light on this issue for me.
Masahiro?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160204/9e5aca69/attachment.sig>
next prev parent reply other threads:[~2016-02-04 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 14:49 [U-Boot] 9c11135 breaks bootz Matthias Weißer
2016-02-04 17:41 ` Tom Rini [this message]
2016-02-05 7:13 ` Masahiro Yamada
2016-02-05 11:58 ` Adam Ford
2016-02-05 12:51 ` Masahiro Yamada
2016-02-06 14:15 ` Adam Ford
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=20160204174127.GI25786@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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