From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lokesh Vutla Date: Thu, 19 May 2016 17:35:28 +0530 Subject: [U-Boot] SPL and FIT images In-Reply-To: <7b3f30d5a0b00c56da4fed38d1c1873e@walle.cc> References: <7b3f30d5a0b00c56da4fed38d1c1873e@walle.cc> Message-ID: <573DAC08.20800@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Michael, On Thursday 19 May 2016 05:16 PM, michael at walle.cc wrote: > Hi, > > I'm looking into the FIT support in the SPL, because we are planning to > load bootloader from a filesystem (on a MMC device); the SPL will be > stored in a write-protected SPI flash. To make sure that a user does not > accidentally put a wrong bootloader image on the filesystem, we would > like to do some kind of compatiblity checking. I guess this can be done > with the FIT image and its compatibility node. Looking into the code I > found out, that FIT images only seems to be supported when the > bootloader is loaded from raw MMC. FIT support for other boot media was recently posted. Links below: Fat FS: http://patchwork.ozlabs.org/patch/618400/ http://patchwork.ozlabs.org/patch/618403/ http://patchwork.ozlabs.org/patch/618405/ SPI: http://patchwork.ozlabs.org/patch/606959/ NAND: http://patchwork.ozlabs.org/patch/609326/ UART: http://patchwork.ozlabs.org/patch/623918/ http://patchwork.ozlabs.org/patch/623919/ http://patchwork.ozlabs.org/patch/623920/ Let me know if you need more info. Thanks and regards, Lokesh > > Simon, since this code is from you, might I ask, why you didn't put it > into the common spl.c (spl_parse_image_header(), etc) so it could be > used for all other methods, too? I just want to make sure, there is no > reason not to do it for our case. > > -michael > _______________________________________________ > U-Boot mailing list > U-Boot at lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot