From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fdt: add fdtcmd env var to allow post processing of device tree before boot
Date: Mon, 04 Aug 2008 15:55:37 -0500 [thread overview]
Message-ID: <48976CC9.4030404@freescale.com> (raw)
In-Reply-To: <F388F9D5-B685-4DD8-ACAC-146A46A1F04E@kernel.crashing.org>
Kumar Gala wrote:
> On Aug 4, 2008, at 3:27 PM, Wolfgang Denk wrote:
>> So just run the needed commands before you run "bootm" as part of your
>> boot command sequence.
>
> This doesnt work. Lets say I want to remove a node or property that
> ft_board_setup() adds. If I do what you are suggesting the node or
> prop will get added back:
>
> fdt addr <FOO>
> fdt boardsetup (we assume this adds /bar/prop)
> fdt rm /bar/prop
> bootm (will call ft_board_setup and add /bar/prop back)
>
> This assumes I know the best location for the device tree before
> "bootm" which I'd argue isn't really true. Especially if my dtb is in
> flash.
Why not? Wouldn't it be just another environment variable, like the
load address for the kernel?
-Scott
next prev parent reply other threads:[~2008-08-04 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 18:46 [U-Boot-Users] [PATCH] fdt: add fdtcmd env var to allow post processing of device tree before boot Kumar Gala
2008-08-04 18:56 ` Wolfgang Denk
2008-08-04 19:49 ` Kumar Gala
2008-08-04 20:19 ` Jerry Van Baren
2008-08-04 20:24 ` Kumar Gala
2008-08-04 20:44 ` Jerry Van Baren
2008-08-04 20:52 ` Kumar Gala
2008-08-04 21:04 ` Wolfgang Denk
2008-08-04 20:27 ` Wolfgang Denk
2008-08-04 20:50 ` Kumar Gala
2008-08-04 20:55 ` Scott Wood [this message]
2008-08-04 22:18 ` Kumar Gala
2008-08-04 22:21 ` Scott Wood
2008-08-04 22:53 ` Wolfgang Denk
2008-08-04 21:07 ` Wolfgang Denk
2008-08-04 22:23 ` Kumar Gala
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=48976CC9.4030404@freescale.com \
--to=scottwood@freescale.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 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.