diff options
| author | Simon Glass <sjg@chromium.org> | 2017-07-24 03:19:42 (GMT) |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2017-07-26 01:21:24 (GMT) |
| commit | 88b233a347378dc51113e9ef7ffe62723c9b7758 (patch) | |
| tree | 29e5fb17e8b3ea0d93f8d51e1c5d03404f9836a3 /README | |
| parent | 85fc970d74d09f33fcdcc649e73c5dc4f5334605 (diff) | |
| download | u-boot-fsl-qoriq-88b233a347378dc51113e9ef7ffe62723c9b7758.tar.xz | |
Convert CONFIG_ENV_IS_IN_NVRAM to Kconfig
This converts the following to Kconfig:
CONFIG_ENV_IS_IN_NVRAM
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 14 |
1 files changed, 0 insertions, 14 deletions
@@ -3412,20 +3412,6 @@ following configurations: Builds up envcrc with the target environment so that external utils may easily extract it and embed it in final U-Boot images. -- CONFIG_ENV_IS_IN_NVRAM: - - Define this if you have some non-volatile memory device - (NVRAM, battery buffered SRAM) which you want to use for the - environment. - - - CONFIG_ENV_ADDR: - - CONFIG_ENV_SIZE: - - These two #defines are used to determine the memory area you - want to use for environment. It is assumed that this memory - can just be read and written to, without any special - provision. - BE CAREFUL! The first access to the environment happens quite early in U-Boot initialization (when we try to get the setting of for the console baudrate). You *MUST* have mapped your NVRAM area then, or |