diff options
author | Simon Glass <sjg@chromium.org> | 2017-07-23 21:19:47 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2017-07-25 21:34:15 -0400 |
commit | b31e065f8999d2dc70f3deb430c9b66a5d0d02ea (patch) | |
tree | 371afa81d57c104e7e6f2ba87468f613f9d6461f /README | |
parent | 337cd3f211223719a173a89e4527475ac22e8a01 (diff) | |
download | u-boot-midas-b31e065f8999d2dc70f3deb430c9b66a5d0d02ea.tar.gz u-boot-midas-b31e065f8999d2dc70f3deb430c9b66a5d0d02ea.tar.bz2 u-boot-midas-b31e065f8999d2dc70f3deb430c9b66a5d0d02ea.zip |
Convert CONFIG_ENV_IS_IN_FAT to Kconfig
This converts the following to Kconfig:
CONFIG_ENV_IS_IN_FAT
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
-rw-r--r-- | README | 44 |
1 files changed, 0 insertions, 44 deletions
@@ -3422,19 +3422,6 @@ environment in RAM: we could work on NVRAM directly, but we want to keep settings there always unmodified except somebody uses "saveenv" to save the current settings. -- CONFIG_ENV_IS_IN_REMOTE: - - Define this if you have a remote memory space which you - want to use for the local device's environment. - - - CONFIG_ENV_ADDR: - - CONFIG_ENV_SIZE: - - These two #defines specify the address and size of the - environment area within the remote memory space. The - local device can get the environment from remote memory - space by SRIO or PCIE links. - BE CAREFUL! For some special cases, the local device can not use "saveenv" command. For example, the local device will get the environment stored in a remote NOR flash by SRIO or PCIE link, @@ -3446,37 +3433,6 @@ but it can not erase, write this NOR flash by SRIO or PCIE interface. environment. If redundant environment is used, it will be copied to CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE. -- CONFIG_ENV_IS_IN_FAT: - Define this if you want to use the FAT file system for the environment. - - - FAT_ENV_INTERFACE: - - Define this to a string that is the name of the block device. - - - FAT_ENV_DEVICE_AND_PART: - - Define this to a string to specify the partition of the device. It can - be as following: - - "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) - - "D:P": device D partition P. Error occurs if device D has no - partition table. - - "D:0": device D. - - "D" or "D:": device D partition 1 if device D has partition - table, or the whole device D if has no partition - table. - - "D:auto": first partition in device D with bootable flag set. - If none, first valid partition in device D. If no - partition table then means device D. - - - FAT_ENV_FILE: - - It's a string of the FAT file name. This file use to store the - environment. - - - CONFIG_FAT_WRITE: - This must be enabled. Otherwise it cannot save the environment file. - Please note that the environment is read-only until the monitor has been relocated to RAM and a RAM copy of the environment has been created; also, when using EEPROM you will have to use getenv_f() |