mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-07-05 18:56:15 +09:00
23869bf80b
The assumed number of environment sectors (always 1) leads to an incorrect top_of_range calculation in fw.env.c when a flash device has an erase block size smaller than the environment data size (number of environment sectors > 1). This change updates the default number of environment sectors to at least cover the size of the environment. Also corrected a false statement about the number of sectors column in fw_env.config. Signed-off-by: Dustin Byford <dustin@cumulusnetworks.com>
23 lines
826 B
Plaintext
23 lines
826 B
Plaintext
# Configuration file for fw_(printenv/setenv) utility.
|
|
# Up to two entries are valid, in this case the redundant
|
|
# environment sector is assumed present.
|
|
# Notice, that the "Number of sectors" is not required on NOR and SPI-dataflash.
|
|
# Futhermore, if the Flash sector size is ommitted, this value is assumed to
|
|
# be the same as the Environment size, which is valid for NOR and SPI-dataflash
|
|
|
|
# NOR example
|
|
# MTD device name Device offset Env. size Flash sector size Number of sectors
|
|
/dev/mtd1 0x0000 0x4000 0x4000
|
|
/dev/mtd2 0x0000 0x4000 0x4000
|
|
|
|
# MTD SPI-dataflash example
|
|
# MTD device name Device offset Env. size Flash sector size Number of sectors
|
|
#/dev/mtd5 0x4200 0x4200
|
|
#/dev/mtd6 0x4200 0x4200
|
|
|
|
# NAND example
|
|
#/dev/mtd0 0x4000 0x4000 0x20000 2
|
|
|
|
# Block device example
|
|
#/dev/mmcblk0 0xc0000 0x20000
|