From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Add env vars describing U-Boot target board
Date: Mon, 21 May 2012 13:22:30 -0600 [thread overview]
Message-ID: <4FBA95F6.2020009@wwwdotorg.org> (raw)
In-Reply-To: <20120521190004.1648620715B@gemini.denx.de>
On 05/21/2012 01:00 PM, Wolfgang Denk wrote:
> Dear Stephen Warren,
>
> In message <1337189793-25367-1-git-send-email-swarren@wwwdotorg.org> you wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This can be useful for generic scripts. For example, rather than hard-
>> coding a script to ext2load tegra-harmony.dtb, it could load
>> ${board_soc}-${board_name}.dtb and hence not need adjustments to
>> run on multiple boards.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> Wolfgang, does this seem like a reasonable feature? If so, can we merge
>> it through the Tegra tree, since the next patch enables this for Tegra.
>> Thanks!
>>
>> common/Makefile | 9 +++++++++
>> common/env_common.c | 15 +++++++++++++++
>> common/env_embedded.c | 15 +++++++++++++++
>> 3 files changed, 39 insertions(+), 0 deletions(-)
>
> Please make this optional - I don't want to have this enforced on all
> boards, whether they want it or not.
Wolfgang,
Thanks for taking a look. The variables are already optional; you need
to set CONFIG_ENV_VAR_* in order for common/env_*.c to add those
variables to the default environment. Is that OK?
next prev parent reply other threads:[~2012-05-21 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 17:36 [U-Boot] [PATCH 1/2] Add env vars describing U-Boot target board Stephen Warren
2012-05-16 17:36 ` [U-Boot] [PATCH 2/2] tegra: enabled CONFIG_ENV_VAR_BOARD_NAME/VENDOR/SOC Stephen Warren
2012-05-16 18:05 ` [U-Boot] [PATCH 1/2] Add env vars describing U-Boot target board Otavio Salvador
2012-05-21 19:00 ` Wolfgang Denk
2012-05-21 19:22 ` Stephen Warren [this message]
2012-05-21 21:53 ` Wolfgang Denk
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=4FBA95F6.2020009@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.