On Mon, Nov 14, 2016 at 11:08 AM, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx> wrote: > So, someone merged a patch which makes mmcblk devices follow the > host controller numbering. > > Now my cubox-i fails to boot correctly because the SD card in the > _only_ SD card slot now gets called "mmcblk1" and not "mmcblk0". > > USDHC1 is wired to the on-microsom WiFi, and never has anything > remotely near a SD card or eMMC present. So, this change is > confusing on these platforms. > > Moreover, this is _going_ to break SolidRun distros if people upgrade > their kernels. > > It may be appropriate for eMMC, but it's not appropriate everywhere. > > This is a user visible _regression_ in 4.9-rc. Whoever did this, > please revert whatever change caused this, and next time limit it > to only eMMC. > > Thanks. I see the same thing on newer kernels, which is why I asked the question. I didn't expect (or even want honestly) a non mmcblk0 boot device and was looking for a way to control that via dt. Now I'm understanding that to avoid this kind of bootloader/kernel dependence issue I should be using UUID's to identify the boot device. >From my testing it looks like the change your looking for occurred some time ago and is somewhere between 4.5 and 4.6 and not a 4.9 regression specifically. Regards, Tim -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
