Hi, I have an embedded device which gets the roots information passed as a kernel parameter root=/dev/mmcblk0p2 Am currently migrating to a new kernel and porting device tree changes to be based on the following dts: https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi.dtsi What I've noticed is that the new kernel/device tree seems to change the index for mmcblk (it was mmcblk0 with the previous combination for mainline 4.14 kernel): [ 1.962308] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.003604] sunxi-mmc 1c0f000.mmc: base:0xe0873000 irq:26 ... ... ... [ 2.092684] mmc1: host does not support reading read-only switch, assuming write-enable [ 2.094600] mmc1: Problem switching card into high-speed mode! [ 2.094725] mmc1: new SDHC card at address 0001 [ 2.095211] mmcblk1: mmc1:0001 00000 3.68 GiB [ 2.097424] mmcblk1: p1 p2 p3 p4 The device tree has the following entries regarded to mmc: &mmc0 { bus-width = <4>; cd-gpios = <&pio 5 6 GPIO_ACTIVE_HIGH>; cd-inverted; pinctrl-names = "default"; pinctrl-0 = <&mmc0_pins_a>, <&mmc0_cd_pin>; boot_device = <0>; status = "okay"; vmmc-supply = <®_vcc3v3>; }; &mmc2 { boot_device = <0>; }; Is there a way to have the index fixed and stable? Be Well, Alan -- 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
