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 -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de "Obviously, a major malfunction has occurred." -- Steve Nesbitt, voice of Mission Control, January 28, 1986, as the shuttle Challenger exploded within view of the grandstands. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot