From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: Fix fdt padding issue for initrd mem_rsv
Date: Thu, 22 Oct 2009 07:48:22 -0400 [thread overview]
Message-ID: <4AE04686.8040001@ge.com> (raw)
In-Reply-To: <1256185791-5492-1-git-send-email-galak@kernel.crashing.org>
Kumar Gala wrote:
> Its possible that we end up with a device tree that happens to be a
> particular size that after we call fdt_resize() we don't have any
> space left for the initrd mem_rsv.
>
> Fix this be adding a second mem_rsv into the size calculation. We
> had one to cover the fdt itself and we have the potential of adding
> a second for the initrd.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Gerald Van Baren <vanbaren@cideas.com>
> ---
> Wolfgang, this has been a long standing bug but only shows up if the fdt
> blob happens to be a particular size. Please include this for the v2009.11
> release.
>
> - k
Thanks,
gvb
next prev parent reply other threads:[~2009-10-22 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 4:29 [U-Boot] [PATCH] fdt: Fix fdt padding issue for initrd mem_rsv Kumar Gala
2009-10-22 11:48 ` Jerry Van Baren [this message]
2009-10-24 20:39 ` Wolfgang Denk
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=4AE04686.8040001@ge.com \
--to=gerald.vanbaren@ge.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