Stephen Warren writes: >Patches to make mmc block devices have static names have been proposed >in the past and rejected. I think the main reason is that the block >device names are (or can be) dynamic, so anything that assumes a >particular naming scheme is simply broken. Why may network devices have static IPs and yet storage devices can't have static names? Isn't insisting on dynamic names the same as insisting on DHCP? The distinction appears to be historical, in that DHCP has been around a long time, but no one cared about boot times of MMC-based devices until relatively recently. Doesn't the same argument apply to all aliases, not to mention "chosen" node? Consider what Russell King said recently: http://thread.gmane.org/gmane.linux.kernel/1532141/focus=1532265 I understand that there is a widespread desire to institute a new level of quality control in the device-tree, but if we are agreeing on a new rule, let's be explicit about it. -- Alison Chaiken Mentor Embedded Software Fremont CA USA GMT-8-- 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
