summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-07-30 10:55:45 +0000
committerTom Warren <twarren@nvidia.com>2012-09-07 13:54:31 -0700
commit573668a24e3e4ed5667332ea656e35021767ea6d (patch)
tree8a21d01b0b9b1cb59cb215d246ebb3e83b44c410 /COPYING
parent300feff3241def7a972a01915b75b7a1e1ec2d62 (diff)
downloadu-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.zip
u-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.tar.gz
u-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.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: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions