On 18 July 2012 11:56, Dirk Behme <dirk.behme@xxxxxxxxxxxx> wrote: > > Similar to [1] we have a device which has two mmc block devices connected: > One external removable and a second internal hard wired one. Depending on > the availability of the external removable mmc card at boot time, the > internal hard wired device becomes mmcblk1 (external mmc card available == > mmcblk0) or mmcblk0 if the external one is not there. This order is given by > the hardware. > > With older, non-DT kernels, we used the hack from [2] to control the > initialization order and force the internal hard wired device to mmcblk0. > > Now, we are switching to a newer, DT based kernel. With a DT based kernel > this hack doesn't seem to work an more. > > Any idea how we could influence the initialization order of the mmc block > devices using a DT based kernel? Ensuring that the internal, hard wired mmc > card is always mapped to mmcblk0? > Doesn't it work by simply by moving the "internal" element before "external" in the array 'struct twl4030_hsmmc_info mmc[]' ? -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
