diff options
author | Simon Glass <sjg@chromium.org> | 2017-08-03 12:21:58 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2017-08-15 08:18:53 -0400 |
commit | 4415f1d1f1c57d43f6bc8ff156554c2b2da45b52 (patch) | |
tree | 0fdd6865c364cb7b68af1e9240a997a0fd686880 /arch/x86/cpu/ivybridge/Kconfig | |
parent | 42a8180d19ad8f45b4639015050bc709caa4f32c (diff) | |
download | u-boot-4415f1d1f1c57d43f6bc8ff156554c2b2da45b52.tar.gz u-boot-4415f1d1f1c57d43f6bc8ff156554c2b2da45b52.tar.xz u-boot-4415f1d1f1c57d43f6bc8ff156554c2b2da45b52.zip |
env: Create a location driver for each location
Set up a location driver for each supported environment location. At
present this just points to the global functions and is not used. A
later patch will switch this over to use private functions in each driver.
There are several special cases here in various drivers to handle
peculiarities of certain boards:
1. Some boards define CONFIG_ENV_IS_IN_FAT and CONFIG_SPL_ENV_SUPPORT but
do not actually load the environment in SPL. The env load code was
optimised out before but with the driver, it is not. Therefore a special
case is added to env/fat.c. The correct fix (depending on board testing
might be to disable CONFIG_SPL_ENV_SUPPORT.
2. A similar situations happens with CONFIG_ENV_IS_IN_FLASH. Some boards
do not actually load the environment in SPL, so to reduce code size we
need to drop that code. A similar fix may be possible with these boards,
or it may be possible to adjust the environment CONFIG settings.
Added to the above is that the CONFIG_SPL_ENV_SUPPORT option does not
apply when the environment is in flash.
Obviously the above has been discovered through painful and time-consuming
trial and error. Hopefully board maintainers can take a look and figure
out what is actually needed.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/x86/cpu/ivybridge/Kconfig')
0 files changed, 0 insertions, 0 deletions