u-boot.git/env, branch v2019.01

env: sata: Fix saveenv issue

2019-01-09T12:13:32+00:00

Wrong env buffer was passed into sata write function, cause the saveenv
not work.

Signed-off-by: Ye Li

env: sata: Add missed env location for SATA boot

2019-01-09T12:13:32+00:00

The env location label ENVL_ESATA is missed in location tables, so
when we configure the ENV in SATA, u-boot fails to get correct env
location and cause boot hang in board_f.

Signed-off-by: Ye Li 
Reviewed-by: Peng Fan

env: sf: define API to override sf environment address

2018-12-04T21:07:36+00:00

Defines env_sf_get_env_addr API to override sf environment address,
required to support multiple environment.

Signed-off-by: Rajesh Bhagat 
Reviewed-by: York Sun

env: allow flash and nand env driver to compile together

2018-12-04T21:07:13+00:00

Define env_ptr as static in flash and nand env driver to
allow these to compile together.

Signed-off-by: Rajesh Bhagat 
Reviewed-by: York Sun

arm64: versal: Add support for new Xilinx Versal ACAPs

2018-10-16T14:53:21+00:00

Xilinx is introducing Versal, an adaptive compute acceleration platform
(ACAP), built on 7nm FinFET process technology. Versal ACAPs combine
Scalar Processing Engines, Adaptable Hardware Engines, and Intelligent
Engines with leading-edge memory and interfacing technologies to deliver
powerful heterogeneous acceleration for any application. The Versal AI
Core series has five devices, offering 128 to 400 AI Engines. The series
includes dual-core Arm Cortex™-A72 application processors, dual-core Arm
Cortex-R5 real-time processors, 256KB of on-chip memory with ECC, more
than 1,900 DSP engines optimized for high-precision floating point with
low latency.

The patch is adding necessary infrastructure in place without enabling
platform which is done in separate patch.

Signed-off-by: Michal Simek

fix: env: Fix the SPI flash device setup for DM mode

2018-09-19T07:02:34+00:00

For some reason the spi_flash_probe_bus_cs() is called
inside the setup_flash_device() with zero values in place
of configurated SPI flash mode and maximum flash speed.
This code causes HALT error during startup environment
relocation on some platforms - namely Armada-38x-GP board.
Fix the function call by replacing zeros with the appropriate
values - CONFIG_ENV_SPI_MAX_HZ and CONFIG_ENV_SPI_MODE.

Signed-off-by: Konstantin Porotchkin 
Cc: Igal Liberman 
Cc: Stefan Roese 
Signed-off-by: Stefan Roese

env: ubi: Add missing ENV_NAME

2018-08-24T20:00:48+00:00

Add missing environment name for UBI, to prevent this NULL in output:
Loading Environment from ...
and rather have a valid UBI there:
Loading Environment from UBI...

Signed-off-by: Marek Vasut

env: Merge Rockchip, Sunxi, Zynq and ZynqMP

2018-08-19T16:14:38+00:00

There is no reason to have the same Kconfig options for different SoCs
separately. The patch is merging them together.

Signed-off-by: Michal Simek 
Acked-by: Maxime Ripard 
[trini: Fix ENV_SIZE around ENV_IS_NOWHERE]
Signed-off-by: Tom Rini 

Signed-off-by: Tom Rini

env: Don't show "Failed" error message

2018-08-10T17:45:34+00:00

"Failed" error message from env_load() only clutters the log with
unnecessary details, as we already have all needed warnings by that
time. Example:

    Loading Environment from FAT... MMC: no card present
    ** Bad device mmc 0 **
    Failed (-5)

Let's only print it in case when DEBUG is defined to keep log clear.

Signed-off-by: Sam Protsenko

u-boot: remove driver lookup loop from env_save()

2018-07-30T11:18:47+00:00

When called with ENVOP_SAVE, env_get_location() only returns the
gd->env_load_location variable without actually checking for
the environment location and priority.

This behaviour causes env_save() to fall into an infinite loop when
the low-level drv->save() call fails.

The env_save() function should not loop through the environment
location list but it should save the environment into the location
stored in gd->env_load_location by the last env_load() call.

Signed-off-by: Nicholas Faustini 
Reviewed-by: Simon Goldschmidt