diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2015-10-11 21:37:41 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2015-10-21 07:46:27 -0600 |
| commit | 4b9f6a669ee22ac4694a3a339e94e8fe30bfad1f (patch) | |
| tree | 578229c582254b2dd27d00bc83b7e79eacff9695 /drivers/mmc | |
| parent | 42913a1c7ad6efae598364f5ea1ae083279b571f (diff) | |
| download | u-boot-imx-4b9f6a669ee22ac4694a3a339e94e8fe30bfad1f.zip u-boot-imx-4b9f6a669ee22ac4694a3a339e94e8fe30bfad1f.tar.gz u-boot-imx-4b9f6a669ee22ac4694a3a339e94e8fe30bfad1f.tar.bz2 | |
x86: Use struct mrc_region to describe a mrc region
Currently struct fmap_entry is used to describe a mrc region.
However this structure contains some other fields that are not
related to mrc cache and causes confusion. Besides, it does not
include a base address field to store SPI flash's base address.
Instead in the mrccache.c it tries to use CONFIG_ROM_SIZE to
calculate the SPI flash base address, which unfortunately is
not 100% correct as CONFIG_ROM_SIZE may not match the whole
SPI flash size.
Define a new struct mrc_region and use it instead.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions