On Thu, Aug 7, 2014 at 12:17 PM, Marek Vasut <ma...@denx.de> wrote: > This patch adds support for generating a kernel fitImage, which is > a a successor to the uImage format. Unlike uImage, which could only > contain the kernel image itself, the fitImage can contain all kinds > of artifacts, like the kernel image, device tree blobs, initramfs > images, binary firmwares etc. Furthermore, the fitImage supports > different kinds of checksums, not only CRC32 like the uImage did. > Last, but not least, fitImage supports signatures such that either > the whole image or it's parts can be signed and then in turn can > be verified by the bootloader. > > So far we only add support for wrapping the kernel image and DTB > into the fitImage. The fitImage uses the sha1 checksum, which is > the default. > > Signed-off-by: Marek Vasut <ma...@denx.de>
Could it be reworked and split in a class? it seems the code is quite big to handle it and I think it will allow for more easy understanding and development if we can rework this code to be move out of kernel.bbclass. It does seem to be an image type. You can take a look how ubifs has been included and do something similar for FIT. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
