Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 28 1月, 2018 8 次提交
  3. 27 1月, 2018 3 次提交
    • M
      env: Initialise all the environments · 1d446087
      由 Maxime Ripard 提交于 
      Since we want to have multiple environments, we will need to initialise
all the environments since we don't know at init time what drivers might
fail when calling load.

Let's init all of them, and only consider for further operations the ones
that have not reported any errors at init time.
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      1d446087
    • M
      env: Pass additional parameters to the env lookup function · 8a3a7e22
      由 Maxime Ripard 提交于 
      In preparation for the multiple environment support, let's introduce two
new parameters to the environment driver lookup function: the priority and
operation.

The operation parameter is meant to identify, obviously, the operation you
might want to perform on the environment.

The priority is a number passed to identify the environment priority you
want to retrieve. The lowest priority parameter (0) will be the primary
source.

Combining the two parameters allow you to support multiple environments
through different priorities, and to change those priorities between read
and writes operations.

This is especially useful to implement migration mechanisms where you want
to always use the same environment first, be it to read or write, while the
common case is more likely to use the same environment it has read from to
write it to.
Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      8a3a7e22
    • M
      cmd: nvedit: Get rid of the env lookup · 9c24dfb2
      由 Maxime Ripard 提交于 
      The nvedit command is the only user of env_driver_lookup_default outside of
the environment code itself, and it uses it only to print the environment
it's about to save to during env save.

As we're about to rework the environment to be able to handle multiple
environment sources, we might not have an idea of what environment backend
is going to be used before trying (and possibly failing for some).

Therefore, it makes sense to remove that message and move it to the
env_save function itself. As a side effect, we also can get rid of the call
to env_driver_lookup_default that is also about to get refactored.
Reviewed-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NLukasz Majewski <lukma@denx.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      9c24dfb2
  5. 26 1月, 2018 5 次提交
  7. 25 1月, 2018 2 次提交
  9. 24 1月, 2018 14 次提交
  11. 23 1月, 2018 8 次提交