On Tue, Nov 19, 2013 at 11:42:17AM -0700, Stephen Warren wrote: > On 11/19/2013 05:28 AM, Russell King - ARM Linux wrote: > > On Mon, Nov 18, 2013 at 03:46:32PM -0700, Stephen Warren wrote: > >> Again, the point is not that it's hard to write the script. As you > >> demonstrated, it's easy. The problem is that then, everybody has to do > >> something different for Tegra, forever. No matter how small the actual > >> cost of doing it is, it's still non-scalable to require that everyone > >> know about this special case. I'm not convinced the issue would be > >> isolated to Tegra either. > > > > That's why there's the facility to allow an override to the script, > > just like there's the facility to override the default script when > > running "make install". > > Again, you are completely missing the point about that not scaling at all. > > But I will go and investigate what it takes to support renaming the > DTBs. Everyone (using Tegra) will have to update their bootloader, but > perhaps that can be dealt with. Setting aside the idea of hard-coding filenames into any bootloader binary, did you catch that the proposed solution would allow you to continue using the dts filenames as they currently are? The find command in my example /sbin/installdtbs script spits out the in-tree dtb filename as it currently stands, and then you do what you want with it in your script. Including, copying it, filename intact, into the location of your choice. How could that possibly require you to upgrade your bootloader? I must admit I'm a bit mystified as to what Tegra is doing that this breaks it so horribly... thx, Jason. -- 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
