On Fri, Aug 25, 2017 at 9:03 PM, Stefano Babic sbabic@denx.de wrote:
Hi Jagan,
On 25/08/2017 16:50, Jagan Teki wrote:
From: Jagan Teki jagan@amarulasolutions.com
U-Boot proper is using DM_MMC so, enable CONFIG_BLK otherwise find_mmc_device failed to detect MMC device.
Signed-off-by: Jagan Teki jagan@amarulasolutions.com
configs/imx6qdl_icore_mmc_defconfig | 1 - configs/imx6qdl_icore_rqs_defconfig | 1 - 2 files changed, 2 deletions(-)
diff --git a/configs/imx6qdl_icore_mmc_defconfig b/configs/imx6qdl_icore_mmc_defconfig index ec39d09..9d61c48 100644 --- a/configs/imx6qdl_icore_mmc_defconfig +++ b/configs/imx6qdl_icore_mmc_defconfig @@ -36,7 +36,6 @@ CONFIG_CMD_EXT4_WRITE=y CONFIG_CMD_FAT=y CONFIG_CMD_FS_GENERIC=y CONFIG_OF_LIST="imx6q-icore imx6dl-icore" -# CONFIG_BLK is not set
OT: it is quite strange that removing a "commented" line we change the behaviour, but that is in this case !
Yeah, this is forcing to use mmc_legacy even with DM_MMC because of SPL need. _BLK will enabled by default with DM_MMC so this make U-Boot proper not to use mmc_legacy and go with BLK.
thanks!