From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env: Setup GD_FLG_ENV_DEFAULT flag when default environment are used
Date: Tue, 31 May 2016 09:40:24 +0200 [thread overview]
Message-ID: <574D3FE8.9090404@xilinx.com> (raw)
In-Reply-To: <3AB374BF-57F5-4D80-A2BD-A45F07CC819F@suse.de>
On 31.5.2016 08:39, Alexander Graf wrote:
>
>
>> Am 31.05.2016 um 07:04 schrieb Michal Simek <michal.simek@xilinx.com>:
>>
>>> On 30.5.2016 21:36, Alexander Graf wrote:
>>>
>>>
>>>> On 05/30/2016 04:11 PM, Michal Simek wrote:
>>>> Setup flag when default environment are used to be able to
>>>> rewrite default distro boot variables based on SoC boot mode.
>>>>
>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>> ---
>>>>
>>>> I didn't find any way how to detect that default or saved variables are
>>>> used. I want to have a flag to be able to rewrite boot_targets variable
>>>> based on boot mode. Especially when SD boot mode is setup than SD should
>>>> be primary boot devices, etc.
>>>> When variables are saved boot_targets will be restored and SoC boot mode
>>>> will be ignored.
>>>> If you know better way how to do it, please let me know.
>>>
>>> You may want to be able to do the same from inside a script, so I guess
>>> we should better have this as an environment variable itself again.
>>
>> Was there any environment in past?
>
> With again I meant "from C as well as from script".
>
>>>
>>> There was a way to have environment variable reads return a value
>>> directly from code rather than go via environment storage. I guess we
>>> could expose the flag through that?
>>
>> If you expose environment variable and then run saveenv this variable
>> will be saved and restored again and your script behaves the same.
>
> Not if we declare the environment variable read as callback ;).
What do you mean?
It is kind of interesting that this is not done already for others SoCs
when you want to use distro config. :-)
Cheers,
Michal
next prev parent reply other threads:[~2016-05-31 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 14:11 [U-Boot] [PATCH] env: Setup GD_FLG_ENV_DEFAULT flag when default environment are used Michal Simek
2016-05-30 19:36 ` Alexander Graf
2016-05-31 5:04 ` Michal Simek
2016-05-31 6:39 ` Alexander Graf
2016-05-31 7:40 ` Michal Simek [this message]
2016-06-01 14:16 ` Alexander Graf
2016-06-01 14:21 ` Michal Simek
2016-06-01 14:24 ` Alexander Graf
2016-06-06 21:28 ` [U-Boot] " Tom Rini
2016-06-06 21:34 ` 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=574D3FE8.9090404@xilinx.com \
--to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox