* Matthijs van Duin matthijsvanduin@gmail.com [170327 09:19]:
On 27 March 2017 at 18:07, Tony Lindgren tony@atomide.com wrote:
Anyways, that still won't help end users are all, this only helps the people who have the TRM fnord instance numbering burnt into their brains :)
It's a numbering consistent across boot, and consistent with u-boot's device numbering, which means the boot script can first load a kernel from mmc $n partition $p and then pass root=/dev/mmcblk${n}p${p} to the kernel.
And that's where people will say "use UUIDs" as the Linux generic solution. Won't help at all making sense of dmesg output though.
See the slot_name solution I just replied with.
I don't see how that is helpful at all. If I just wanted some DT-specified label I can slap some property onto the DT nodes and access it via the of_node symlink. This is e.g. what I do for uio devices on beaglebones:
SUBSYSTEM=="uio", SYMLINK+="uio/%s{device/of_node/uio-alias}"
Sure.
So I guess no still no Linux generic solution in sight.
Regards,
Tony