diff options
author | Andreas Fenkart <andreas.fenkart@digitalstrom.com> | 2016-08-11 21:39:17 +0200 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2016-08-15 18:46:40 -0400 |
commit | 183923d3e412500bdc597d1745e2fb6f7f679ec7 (patch) | |
tree | 3dbd12d06714b5929544c3dddf78bb0bf7ff110d /net | |
parent | 7e270ec3af02d2358f9a454ba0d0bb39f07d14b6 (diff) | |
download | u-boot-imx-183923d3e412500bdc597d1745e2fb6f7f679ec7.zip u-boot-imx-183923d3e412500bdc597d1745e2fb6f7f679ec7.tar.gz u-boot-imx-183923d3e412500bdc597d1745e2fb6f7f679ec7.tar.bz2 |
tools/env: ensure environment starts at erase block boundary
56086921 added support for unaligned environments access.
U-boot itself does not support this:
- env_nand.c fails when using an unaligned offset. It produces an
error in nand_erase_opts{drivers/mtd/nand/nand_util.c}
- in env_sf/env_flash the unused space at the end is preserved, but
not in the beginning. block alignment is assumed
- env_sata/env_mmc aligns offset/length to the block size of the
underlying device. data is silently redirected to the beginning of
a block
There is seems no use case for unaligned environment. If there is
some useful data at the beginning of the the block (e.g. end of u-boot)
that would be very unsafe. If the redundant environments are hosted by
the same erase block then that invalidates the idea of double buffering.
It might be that unaligned access was allowed in the past, and that
people with legacy u-boot are trapped. But at the time of 56086921
it wasn't supported and due to reasons above I guess it was never
introduced.
I prefer to remove that (unused) feature in favor of simplicity
Signed-off-by: Andreas Fenkart <andreas.fenkart@digitalstrom.com>
Acked-by: Stefan Agner <stefan.agner@toradex.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions