summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-07-30 10:55:45 +0000
committerAndy Fleming <afleming@freescale.com>2012-09-05 17:32:42 -0500
commit1c1ec3c0b599e3759f5e232a46f5460221941097 (patch)
treec2c974621277db94d83075ff8313acf7242df6fa /drivers
parent9404a5fc7cb58bc56152dfd7d355902dfb666f8b (diff)
downloadu-boot-imx-1c1ec3c0b599e3759f5e232a46f5460221941097.zip
u-boot-imx-1c1ec3c0b599e3759f5e232a46f5460221941097.tar.gz
u-boot-imx-1c1ec3c0b599e3759f5e232a46f5460221941097.tar.bz2
tegra: put eMMC environment into the boot sectors
When I set up Tegra's config files to put the environment into eMMC, I assumed that CONFIG_ENV_OFFSET was a linearized address relative to the start of the eMMC device, and spanning HW partitions boot0, boot1, general* and the user area in order. However, it turns out that the offset is actually relative to the beginning of the user area. Hence, the environment block ended up in a different location to expected and documented. Set CONFIG_SYS_MMC_ENV_PART=2 (boot1) to solve this, and adjust CONFIG_ENV_OFFSET to be relative to the start of boot1, not the entire eMMC. Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Andy Fleming <afleming@freescale.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions