From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 6/8] fdt: cmd_fdt: Call fdt_chosen() from "fdt boardsetup"
Date: Tue, 02 Oct 2012 12:26:05 +0200 [thread overview]
Message-ID: <506AC13D.4030507@denx.de> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A6B2865@039-SN1MPN1-001.039d.mgd.msft.net>
On 09/27/2012 10:43 PM, McClintock Matthew-B29882 wrote:
>>>>> By calling fdt_chosen(), the chosen node will be updated /
>>>>> created by the "fdt boardsetup" command. This is useful for
>>>>> setting of the kernel commandline via the "bootargs"
>>>>> env variable.
>>>>>
>>>>> With this change, the "fdt boardsetup" can be used to prepare
>>>>> the DT blob for SPL booting. The patched DT blob can be saved
>>>>> to flash and can be used by the SPL U-Boot version directly
>>>>> for Linux booting.
>>>>>
>>>>> Signed-off-by: Stefan Roese <sr@denx.de>
>>>>> ---
>>>>>
>>>>> common/cmd_fdt.c | 4 +++-
>>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> There are possibly some workflows this breaks. I can't remember
>>>> if for AMP boot we need to do something between ft_board_setup()
>>>> and fdt_chosen()
>>>
>>> Could you please elaborate what exactly you fear here? Is this a NACK
>>> for this patch?
>>
>> Possibly. I've got to find our docs on how we do 2-core AMP booting sequence w/regards to device tree.
>
> See if this works:
>
> http://www.freescale.com/infocenter/index.jsp?topic=%2FQORIQSDK%2F2151493.html
Kumar, did you find the time to check/test this? I would really like to
know if this patch is okay with you.
Thanks,
Stefan
next prev parent reply other threads:[~2012-10-02 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 9:11 [U-Boot] [PATCH v3 6/8] fdt: cmd_fdt: Call fdt_chosen() from "fdt boardsetup" Stefan Roese
2012-09-26 13:36 ` Kumar Gala
2012-09-26 14:20 ` Stefan Roese
2012-09-27 20:28 ` Kumar Gala
2012-09-27 20:43 ` McClintock Matthew-B29882
2012-10-02 10:26 ` Stefan Roese [this message]
2012-10-03 0:57 ` McClintock Matthew-B29882
2012-10-04 7:43 ` Stefan Roese
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=506AC13D.4030507@denx.de \
--to=sr@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