From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: Fix fdt padding issue for initrd mem_rsv
Date: Sat, 24 Oct 2009 22:39:42 +0200 [thread overview]
Message-ID: <20091024203942.D00CD185D4AA@gemini.denx.de> (raw)
In-Reply-To: <1256185791-5492-1-git-send-email-galak@kernel.crashing.org>
Dear Kumar Gala,
In message <1256185791-5492-1-git-send-email-galak@kernel.crashing.org> you 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>
> ---
> 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
>
> common/fdt_support.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
Applied, thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"The bad reputation UNIX has gotten is totally undeserved, laid on by
people who don't understand, who have not gotten in there and tried
anything." -- Jim Joyce, owner of Jim Joyce's UNIX Bookstore
prev parent reply other threads:[~2009-10-24 20:39 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
2009-10-24 20:39 ` Wolfgang Denk [this message]
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=20091024203942.D00CD185D4AA@gemini.denx.de \
--to=wd@denx.de \
--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 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.