On Tue, Nov 12, 2013 at 08:40:09PM +0100, Andrew Lunn wrote: > > 2) right now: distributions are creating utilities, such a flash-kernel > > in Debian, that pick from a slew of dtbs, append it to the zImage, and > > create the uImage. The bootloaders in these installs don't have support > > for fdt. > > > > Our problem (as I see it) is that #2 is creating an ABI out of something > > we never realized would become an ABI, the filenames created by 'make > > dtbs'. > > Well, flash-kernel could be taught how to parse .dtb files to get the > compatibility strings out of them, rather than use filenames. > > It might still be early enough to give distributions some guidelines > about what DT folks consider ABI and what is not. How they should find > a fitting .dtb file and how they should not. True, but this isn't a 'search /boot/config-X for CONFIG_Y so we can configure for Z' *cough* *grub* *cough*. flash-kernel currently doesn't have any more correct way to select dtbs than by filename. It's normal to look for arch/<arch>/boot/zImage after a build. Module names are not 1-1 with object files or source files, they are unique, and static. Our failure was not providing a similar ABI for the dtbs. imho, we messed up, so we should fix it. 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
