On Fri, Apr 29, 2016 at 05:31:31PM -0700, Peter Hurley wrote: > FWIW, there is already a defacto expectation by boot configurations in the > field that a given mmc block device is stable across boots. The reality > is that 100000's of kernel command lines look like: > > root=/dev/mmcblk0p2 Thankfully, MMC does generally give a stable naming across reboots - I have platforms with eMMC and SD (eg, the SDP4430 board which is in the test farm) and only when things change in the kernel does the MMC device name change. Changes in device ordering can be provoked by the order in which entries in the DT file appear, and hence the order in which the host SD interfaces are probed by the kernel. When it changed, I switched from using the device specifier to using a UUID. Now I have no problems since I no longer care which MMC block device ends up as the SD card. The kernel there is TFTP'd too. -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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
