test: fastboot: Avoid using mmc1

The bootflow tests need to use an MMC with an associated backing file
containing a filesystem. Update the fastboot tests to cope with this.

Signed-off-by: Simon Glass <sjg@chromium.org>

diff --git a/test/dm/fastboot.c b/test/dm/fastboot.c
index e7f8c362b85e5cf43aa598fdcd385328971f3a25..758538d0e85e5a501ccb83c099cecc50d5ea9028 100644 (file)
--- a/test/dm/fastboot.c
+++ b/test/dm/fastboot.c
@@ -81,9 +81,9 @@ static int dm_test_fastboot_mmc_part(struct unit_test_state *uts)
                                                  &part_info, response));
        ut_asserteq(0, fastboot_mmc_get_part_info("0.0:0", &fb_dev_desc,
                                                  &part_info, response));
-       ut_asserteq(0, fastboot_mmc_get_part_info("1", &fb_dev_desc,
+       ut_asserteq(0, fastboot_mmc_get_part_info("2", &fb_dev_desc,
                                                  &part_info, response));
-       ut_asserteq(0, fastboot_mmc_get_part_info("1.0", &fb_dev_desc,
+       ut_asserteq(0, fastboot_mmc_get_part_info("2.0", &fb_dev_desc,
                                                  &part_info, response));
        ut_asserteq(1, fastboot_mmc_get_part_info(":1", &fb_dev_desc,
                                                  &part_info, response));