10 Jan, 2012
6 commits
-
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Only use the values from the image tag if it is valid. Always create
the CFE, NVRAM and linux partitions, to allow flashing a new image even
if the old is invalid without overwriting CFE or NVRAM.Signed-off-by: Jonas Gorski
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Instead of referencing the sizes of fixed partitions, use the
precomputed CFE/NVRAM lengths.Signed-off-by: Jonas Gorski
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
The CFE boot loader on BCM63XX platforms assumes itself and the NVRAM
partition to be 64 KiB (or erase block sized, if larger).
Ensure this assumption is also met when creating the partitions to
prevent accidential erasure of CFE or NVRAM.Signed-off-by: Jonas Gorski
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Recent CFEs do not contain the CFE1CFE1 magic anymore, so check for the
"cfe-v" version marker string instead. As very old CFEs do not have
this string, leave the CFE1CFE1 magic as a fallback for detection.Signed-off-by: Jonas Gorski
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
Recent BCM63XX devices support a variety of flash types (parallel, SPI,
NAND) and share the partition layout. To prevent code duplication make
the CFE partition parsing code a stand alone mtd parser to allow SPI or
NAND flash drivers to use it.Signed-off-by: Jonas Gorski
Acked-by: Florian Fainelli
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
