[Buildroot] [PATCH v4 3/7] barebox: support custom barebox output image name
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Wed Apr 6 14:53:43 UTC 2016
Hello,
On Tue, 5 Apr 2016 01:20:13 +0200, Arnout Vandecappelle wrote:
> > +config BR2_TARGET_BAREBOX_OUTPUT_IMAGE_FILE
> > + string "Output image filename"
>
> With my suggestion of BR2_TARGET_BAREBOX_IMAGE_NAME, this should be changed
> to e.g. BR2_TARGET_BAREBOX_OUTPUT_IMAGE_NAME. The prompt looks OK though.
>
>
> However, on second thought I'm wondering if it is really needed. For u-boot or
> the kernel, we always copy the images with the same name as they were built. If
> that is not what the ROM boot loader expects, the name can be changed in the
> image generation script. For example, genimage.cfg could contain:
>
> image boot.vfat {
> vfat {
> file MLO {
> "barebox-am33xx-beaglebone-mlo.img"
> }
> file barebox.img {
> "barebox-am33xx-beaglebone.img"
> }
> }
> size = 8M
> }
>
>
> What do you think?
I agree, we don't do this for U-Boot/kernel or any other thing, so I
don't think we should be doing it for Barebox.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
More information about the buildroot
mailing list