[meta-xilinx] Board specific kernel config not applied correctly

[Andreas Galauner]

On 14/04/14 10:26, Nathan Rossi wrote:
> The issues you are having are due to the scripting of how the configs are merged, and how the kernel processes the .config. Essentially the kernel parses .configs reverse ordered (to what you mentioned above), the configs that are set first are overridden by configs that are set later. The other problem here is that because the MACHINE_KCONFIG variable is set with _append, it is hard to get it to remove or place your own cfg fragments ordered after the defconfig.
> 
> The reason the microblaze configs get away with this is that they override configs which are not set in the defconfig.

Yeah, that's something I found out too after endless hours of debugging
the build system ;)


> I have pushed some changes which should resolve these issues, and should allow you to set MACHINE_KCONFIG += "copter_microzed.kconfig.cfg" in your machine.conf, and give precedence to your cfg fragment. Also this should work for linux-xlnx and linux-yocto recipes. You should also now be able to completely control the MACHINE_KCONFIG variable, as the setting is now completely done at the machine level, look at machine-xilinx-default.inc.

Cool, thanks.
Unfortunately I can't try your changes, because I already switched to a
modified linux-yocto-custom recipe with a patched xilinx kernel tree for
my own platform. The mechanisms there work a bit different.

- Andy