On Fri, Apr 29, 2016 at 02:17:45PM -0700, Doug Anderson wrote: > Hi, > > On Fri, Apr 29, 2016 at 2:13 PM, Russell King - ARM Linux > <linux@xxxxxxxxxxxxxxxx> wrote: > > On Fri, Apr 29, 2016 at 01:04:48PM -0700, Doug Anderson wrote: > >> Russell, > >> > >> On Fri, Apr 29, 2016 at 12:57 PM, Russell King - ARM Linux > >> <linux@xxxxxxxxxxxxxxxx> wrote: > >> >> * Presumably on a PC you've got an extra bit in the middle (like grub > >> >> or something like that) that can help you resolve your UUIDs even if > >> >> you get your kernel from somewhere else. > >> > > >> > You are over-estimating what grub does. Grub doesn't resolve UUIDs at > >> > all. Grub just passes the kernel arguments in its configuration file > >> > for the entry it is booting to the kernel. It's a static configuration > >> > found in /boot/grub/grub.conf. > >> > > >> > It doesn't probe devices for UUIDs. > >> > >> OK. The point was: if folks on PCs have a workflow that works for > >> them, wonderful. That workflow doesn't work so great for me. My > >> workflow doesn't hurt them. Why is it bad? > > > > This discussion is over, since you're not willing to actually discuss > > it (illustrated by you cutting and pasting this same thing four > > times in your reply.) > > > > My NAK stands until such time that you can partake in a reasonable > > discussion. > > The point of pasting it several times was that you'd answer it. > Apparently that failed. > > Perhaps you could answer the question I posed? No, because you haven't taken the time to think and consider my reply, which gives you insight into how your "problem" is no different from the situation that everyone else has, where it isn't a problem. I think the "problem" here is that you've got used to coreboot doing something that very few other boot loaders do, namely it automatically extracting a rootfs UUID for you. The rest of the world doesn't have that luxury. So, instead, you want to stuff more code into the kernel to work around what you think is a problem - a problem which seems to be unique to yourself. The UUID and label solutions were created by x86 people to work around exactly this dynamic device problem, and as my previous replies have shown, it is superior to fixing the device assignment as you're trying to do. However, I don't expect that you'll like this answer, and you'll probably just re-post your same question after each and every paragraph rather than considering whether the already existing solutions could solve your "problem". So I'm just wasting my time. This is my last reply. -- 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
