On 11/11/2011 14:26, Loïc Minier wrote:
On Fri, Nov 11, 2011, Daniel Schwierzeck wrote:
ALL-$(CONFIG_UBOOT_IMG) += $(obj)u-boot.img ALL-$(CONFIG_UBOOT_IMX) += $(obj)u-boot.imx ALL-$(CONFIG_UBOOT_KWB) += $(obj)u-boot.kwb
then you can define CONFIG_UBOOT_KWB or CONFIG_UBOOT_IMX in your board config if needed
That'd be a fine solution for me if others agree it's the right approach; ideally, we would even set CONFIG_UBOOT_IMX when CONFIG_IMX_CONFIG is set (not sure where though).
Sorry to bring a dead thread to new life...
The issue is not yet solved and I am asking if we can do something for the incoming release 2012.04. I would prefer we do not add a new switch CONFIG_UBOOT_IMX into the configuration file, because it is possible to have the same u-boot image running on different storages, for example on NAND or NOR, and they have different offsets. This means different imximage (header), while u-boot itself (binary) remains the same. So this information should be not interpreted by the compiler.
Rereading the thread a major point is that we must not change the main Makefile. What about if the changes suggested in the patch are put into arch/arm/cpu/armv7/config.mk ?
Best regards, Stefano Babic