From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/5] Allow U-Boot scripts to be placed in a .env file
Date: Fri, 25 Oct 2013 16:34:37 +0100 [thread overview]
Message-ID: <526A8F8D.200@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ2tyOQJh+Y_9gp-mB2m6QzabFfscF5d03FV=P6L8FTrvQ@mail.gmail.com>
On 10/20/2013 09:47 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Wed, Jun 26, 2013 at 1:56 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 06/24/2013 02:46 PM, Simon Glass wrote:
>>> At present U-Boot environment variables, and thus scripts, are defined
>>> by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large amounts of text
>>> to this file and dealing with quoting and newlines is harder than it
>>> should be. It would be better if we could just type the script into a
>>> text file and have it included by U-Boot.
>>>
>>> Add a feature that brings in a .env file associated with the board
>>> config, if present. To use it, create a file in a board/<vendor>/env
>>> directory called <board>.env (or common.env if you want the same
>>> environment for all boards).
>
> [well perhaps it is time to get back to this]
>
>> I'm not entirely sure how useful common.env is.
>>
>> Consider that many different Tegra boards, from different vendors, all
>> share the same environment. For example boards/compulab/trimslice shares
>> the core environment with boards/nvidia/*. IIUC, common.env wouldn't
>> work in this case, since the vendor is different. To solve that, we
>> could easily symlink board/compulab/env/trimslice.env ->
>> board/nvidia/env/something.env. But in that case, why not always rely on
>> creating symlinks, instead of having the common.env fallback work too?
>> Also consider that compulab makes a ton of boards only some of which use
>> Tegra, so even a common.env in board/compulab/env wouldn't be that useful.
>
> I find symlinks a pain in the source tree. I think they should be the
> exception rather than the rule. This feature here mirrors the current
> board/<vendor>/common directory which is fairly widely used.
Well, we use includes rather than symlinks, e.g. put the following into
boards/compulab/env/trimslice.env:
#include <boards/nvidia/env/something.env>
> $ ls board/*/common -d |wc -l
> 21
>
> I feel that Compulab can do their own common file if they want it
I'd rather as many board worked the same way as possible; that makes it
much easier for distros, and even developers. We shouldn't go out of our
way to make that hard.
> A file common to all Tegra perhaps belongs in arch/arm/.. somewhere?
That might be a better location, yes.
next prev parent reply other threads:[~2013-10-25 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 20:46 [U-Boot] [PATCH v2 0/5] env: Add support for environment files Simon Glass
2013-06-24 20:46 ` [U-Boot] [PATCH v2 1/5] sandbox: Support 'env import' and 'env export' Simon Glass
2013-06-24 20:46 ` [U-Boot] [PATCH v2 2/5] Make 'run' use run_command_list() instead of run_command() Simon Glass
2013-06-24 20:46 ` [U-Boot] [PATCH v2 3/5] Allow U-Boot scripts to be placed in a .env file Simon Glass
2013-06-26 19:56 ` Stephen Warren
2013-10-20 20:47 ` Simon Glass
2013-10-25 15:34 ` Stephen Warren [this message]
2013-06-24 20:46 ` [U-Boot] [PATCH v2 4/5] env: Allow environment files to use the C preprocessor Simon Glass
2013-06-26 20:05 ` Stephen Warren
2013-10-20 21:09 ` Simon Glass
2013-06-24 20:46 ` [U-Boot] [PATCH v2 5/5] RFC: tegra: Convert to using environment files Simon Glass
2013-06-26 20:16 ` Stephen Warren
2013-10-20 21:15 ` Simon Glass
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=526A8F8D.200@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox