From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL and FIT images
Date: Thu, 19 May 2016 17:35:28 +0530 [thread overview]
Message-ID: <573DAC08.20800@ti.com> (raw)
In-Reply-To: <7b3f30d5a0b00c56da4fed38d1c1873e@walle.cc>
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
next prev parent reply other threads:[~2016-05-19 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 11:46 [U-Boot] SPL and FIT images michael at walle.cc
2016-05-19 12:05 ` Lokesh Vutla [this message]
2016-05-19 15:38 ` michael at walle.cc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573DAC08.20800@ti.com \
--to=lokeshvutla@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox