U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] lib: Add CONFIG_FDT_IGNORE_FIXUP_MEMORY_NODE
Date: Mon, 07 Apr 2014 08:53:39 +0200	[thread overview]
Message-ID: <20140407065339.499CC3804B4@gemini.denx.de> (raw)
In-Reply-To: <1396846600-15386-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>

Dear Nobuhiro Iwamatsu,

In message <1396846600-15386-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com> you wrote:
> Usually, when CONFIG_OF_LIBFDT is enabled, U-Boot is set to
> the FDT memory information that is set in the U-Boot. This patch
> disables this behavior.
> 
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> ---
>  README                   | 8 ++++++++
>  arch/arm/lib/bootm-fdt.c | 2 ++
>  2 files changed, 10 insertions(+)

Please explain why you would want to do this.  To me it makes no
sense.  Either U-Boot knows the correct memory size, then it should
pass it to Linux.  Or it does not, then U-Boot should be fixed.

Also, I object that your implementation is ARM specific.  If such a
feature gets added, it should be architecture independent.

Thanks.

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
To be a winner, all you need to give is all you have.

  reply	other threads:[~2014-04-07  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  4:56 [U-Boot] [PATCH] lib: Add CONFIG_FDT_IGNORE_FIXUP_MEMORY_NODE Nobuhiro Iwamatsu
2014-04-07  6:53 ` Wolfgang Denk [this message]
2014-04-07 17:41   ` Tom Rini
2014-04-08  1:54     ` Nobuhiro Iwamatsu
2014-04-08  1:50   ` Nobuhiro Iwamatsu
2014-04-08 13:05     ` Wolfgang Denk
2014-04-08 16:17       ` Tom Rini
2014-04-08 16:39         ` thomas.langer at lantiq.com
2014-04-09  3:20         ` Masahiro Yamada
2014-04-09 12:27           ` Tom Rini

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=20140407065339.499CC3804B4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox