Hi Jagan, I've just tried this out on x530 and db-88f6820-amc (both ARCH_MVEBU).
On Fri, Jan 18, 2019 at 8:23 PM Jagan Teki <ja...@amarulasolutions.com> wrote: > > Migrate CONFIG_BUILD_TARGET into Kconfig. > > Signed-off-by: Jagan Teki <ja...@amarulasolutions.com> > --- <snip> > diff --git a/Kconfig b/Kconfig > index aff7b2e00a..15b79259a8 100644 > --- a/Kconfig > +++ b/Kconfig > @@ -224,6 +224,19 @@ config BUILD_ROM > which are not shipped in the U-Boot source tree. > Please, see doc/README.x86 for details. > > +config BUILD_TARGET > + string "Build target special images" > + default "u-boot-with-spl.sfp" if ARCH_SOCFPGA > + default "u-boot-spl.kwb" if ARCH_MVEBU && SPL_BUILD It looks like this doesn't work as expected. Perhaps because SPL_BUILD is a bit special. Should this hang of CONFIG_SPL or CONFIG_SUPPORT_SPL instead? > + default "u-boot-elf.srec" if RCAR_GEN3 > + default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI > + help > + Some SoCs need special image types (e.g. U-Boot binary > + with a special header) as build targets. By defining > + CONFIG_BUILD_TARGET in the SoC / board header, this > + special image will be automatically built upon calling > + make / buildman. > + > endmenu # General setup > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
