Hi Wolfgang, On Tue, Jul 19, 2016 at 9:14 AM, Wolfgang Denk <w...@denx.de> wrote: > Dear Mario, > > In message > <can1kzortfqcvooz5o5j7-r-t5ytdbrcqdbhgc4ghamx1suh...@mail.gmail.com> you > wrote: >> >> It is, but the problem is that adding a new type, like "ubootimage," or >> something like that, would not be as easy as with the platform-specific image >> types (like, e.g. "rkimage"), which only appear in mkimage, because we'd have >> to account for this new type in common/bootm.c (essentially, add a lot of >> additional "|| images.os.type == IH_TYPE_UBOOT"). > > There is no need for a new type. IH_TYPE_FIRMWARE should be used for > this; see also comments around [1] > > [1] http://git.denx.de/?p=u-boot.git;a=blob;f=include/image.h#l228 > > Best regards, > > Wolfgang Denk >
Ah, OK, I thought that IH_TYPE_FIRMWARE should exclusively be used for firmware updates, like the comment said, not for actually *running* the firmware. In that case the work is more manageable (there's still some changes needed, because common/image-fit.c refuses to boot images with firmware type, too). I'll look into preparing a v2. Thanks for the help! Best regards, Mario _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
