From: Vagrant Cascadian <vagrant@aikidev.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 5/5] mx6cuboxi: Load the correct 'fdt_file' variable
Date: Sat, 25 Apr 2015 09:22:12 -0700 [thread overview]
Message-ID: <87wq10p497.fsf@aikidev.net> (raw)
In-Reply-To: <553B2EC1.8080203@denx.de>
On 2015-04-24, Stefano Babic wrote:
> On 25/04/2015 01:47, Vagrant Cascadian wrote:
>> On 2015-04-24, Fabio Estevam wrote:
>>> Instead of hardcoding the 'fdt_file' variable, let's detect the SoC and
>>> board variant on the fly and change the dtb name.
>> ...
>>> diff --git a/include/configs/mx6cuboxi.h b/include/configs/mx6cuboxi.h
>>> index 5d58b16..c3cf633 100644
>>> --- a/include/configs/mx6cuboxi.h
>>> +++ b/include/configs/mx6cuboxi.h
>> ...
>>> #define CONFIG_EXTRA_ENV_SETTINGS \
>>> "script=boot.scr\0" \
>>> "image=zImage\0" \
>>> - "fdt_file=" CONFIG_DEFAULT_FDT_FILE "\0" \
>>> + "check_suffix=" \
>>> + "if is_hummingboard; then " \
>>> + "setenv dts_suffix -hummingboard.dtb;" \
>>> + "else " \
>>> + "setenv dts_suffix -cubox-i.dtb;" \
>>> + "fi; "\
>>> + "setenv fdt_file ${dts_prefix}${dts_suffix};" \
>>> "fdt_addr=0x18000000\0" \
>>
>> The setenv fdt_file line needs to terminate with "\0",
>
> Are you sure ? I think Fabio's intention is to have setenv fdt_file as
> part of check_suffix, and it is not if you add a trailing \0
Well, if you don't append the \0, then fdt_addr=0x18000000 is appended
to check_suffix, and fdt_addr is left unset... At least, that's what a
booted system showed.
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150425/dd2bcb5b/attachment.sig>
next prev parent reply other threads:[~2015-04-25 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 11:46 [U-Boot] [PATCH v3 1/5] mx6cuboxi: Fix the defconfig name Fabio Estevam
2015-04-24 11:46 ` [U-Boot] [PATCH v3 2/5] mx6cuboxi: Prepare for multi SoC support Fabio Estevam
2015-04-24 11:46 ` [U-Boot] [PATCH v3 3/5] mx6cuboxi: Introduce multi-SoC support Fabio Estevam
2015-04-24 12:27 ` Stefano Babic
2015-04-24 12:29 ` Fabio Estevam
2015-04-24 11:46 ` [U-Boot] [PATCH v3 4/5] mx6cuboxi: Differentiate Cubox-i and Hummingboard Fabio Estevam
2015-04-24 11:46 ` [U-Boot] [PATCH v3 5/5] mx6cuboxi: Load the correct 'fdt_file' variable Fabio Estevam
2015-04-24 23:47 ` [U-Boot] [U-Boot, v3, " Vagrant Cascadian
2015-04-25 6:05 ` Stefano Babic
2015-04-25 15:30 ` Fabio Estevam
2015-04-25 17:02 ` Vagrant Cascadian
2015-04-25 16:22 ` Vagrant Cascadian [this message]
2015-04-25 16:58 ` [U-Boot] [PATCH v3 " 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=87wq10p497.fsf@aikidev.net \
--to=vagrant@aikidev.net \
--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