diff options
| author | Tom Rini <trini@ti.com> | 2013-04-05 06:21:44 +0000 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2013-04-08 11:29:34 -0400 |
| commit | c3d2c24f6cebd115cdc577e13520045a30ca5dc6 (patch) | |
| tree | 4378b7ae0b985a233e66ffd4bb80c75af0c6e953 /tools/xway-swap-bytes.c | |
| parent | d3d82e9fc69e284fa66ca82c8623f7de64a28130 (diff) | |
| download | u-boot-imx-c3d2c24f6cebd115cdc577e13520045a30ca5dc6.zip u-boot-imx-c3d2c24f6cebd115cdc577e13520045a30ca5dc6.tar.gz u-boot-imx-c3d2c24f6cebd115cdc577e13520045a30ca5dc6.tar.bz2 | |
OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC
In the case of booting from certain peripherals, such as UART, we must
not see what the device descriptor says for RAW or FAT mode because in
addition to being nonsensical, it leads to a hang. This is why we have
a test currently for the boot mode being within range. The problem
however is that on some platforms we get MMC2_2 as the boot mode and not
the defined value for MMC2, and in others we get the value for MMC2_2.
This is required to fix eMMC booting on omap5_uevm.
Tested on am335x_evm (UART, NAND, SD), omap3_beagle (NAND, SD on
classic, SD only on xM rev C5) and omap5_uevm (SD, eMMC).
Signed-off-by: Tom Rini <trini@ti.com>
Diffstat (limited to 'tools/xway-swap-bytes.c')
0 files changed, 0 insertions, 0 deletions