diff options
| author | Marcel Ziswiler <marcel.ziswiler@toradex.com> | 2013-08-12 10:37:32 +0200 |
|---|---|---|
| committer | Marcel Ziswiler <marcel.ziswiler@toradex.com> | 2013-08-12 10:37:32 +0200 |
| commit | d63f3c73a767b82ba1e28c30a46a1e88616ed66e (patch) | |
| tree | 572ab70727626189353b577e0840d60b7fa61c9c /include/configs/apalis_t30.h | |
| parent | 1cf83224ac11e2ea1a0b3546b27ecd9a59fac247 (diff) | |
apalis/colibri_t30: implement emmc pt offset auto detection
In preparation for the new Apalis T30 SKUs implement eMMC PT offset
auto detection.
The PT offset has been calculated from the .cfg eMMC partition
configuration file using virtual linearised addressing across all eMMC
regions as expected by nvflash.
Due to the lack of a region control mechanism in nvflash/.cfg flashing
utility in order to obtain the actual PT offset from the start of the
user region the size of the boot regions must be subtracted.
An eMMC device is specified to have 0 or 2 boot regions and they must
have the same size ranging from 0 to 2 MiB. The boot region size can be
queried from the device through the BOOT_SIZE_MULT field of the
response to the EXT_CSD command sequence.
Tested on initial samples of Apalis T30 1GB V1.0A,
Apalis T30 2GB V1.0B, Apalis T30 2GB V1.0C and Colibri T30 V1.1C.
Diffstat (limited to 'include/configs/apalis_t30.h')
0 files changed, 0 insertions, 0 deletions