From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/7] SPL: FIT: Bring the SPL_LOAD_FIT path in line with documentation
Date: Wed, 10 Mar 2021 12:04:35 -0600 [thread overview]
Message-ID: <20210310180442.746517-1-mr.nuke.me@gmail.com> (raw)
When I wrote commit 4afc4f37c70e ("doc: FIT image: Clarify format and
simplify syntax"), I did not expect it to go through without
objection. I didn't also write the code to go along with it. This
series fixes that by updating one of the three FIT code paths to be
compliant.
There are three code paths that deal with loading a FIT:
* 'bootm' command
* SPL_LOAD_FIT
* SPL_LOAD_FIT_FULL
I chose to start with SPL_LOAD_FIT, because that's the code I'm most
familiar with. Also, by its simplicity, it is the most generic FIT
loading code, and the easiest to make compliant.
I also chose not to fix every nook and cranny because nobody is using
those corner cases -- as evidenced by the lack of support. Instead, I
chose to document known limitations.
Alexandru Gagniuc (7):
spl: fit: Don't overwrite previous loadable if "load" is missing
doc: FIT image: Introduce "u-boot,fpga-legacy" property
spl: fit: Move FPGA loading code to separate functions
spl: fit: Warn if FIT contains "fpga" property in config node
spl: fit: Support loading FPGA images from list of "loadables"
Kconfig: Document the limitations of the simple SPL_LOAD_FIT path
doc: FIT image: Update FPGA example to make use of "loadables"
common/Kconfig.boot | 10 +++
common/spl/spl_fit.c | 113 ++++++++++++++++++++------
doc/uImage.FIT/multi-with-fpga.its | 3 +-
doc/uImage.FIT/source_file_format.txt | 1 +
4 files changed, 99 insertions(+), 28 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-10 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:04 Alexandru Gagniuc [this message]
2021-03-10 18:04 ` [PATCH 1/7] spl: fit: Don't overwrite previous loadable if "load" is missing Alexandru Gagniuc
2021-03-15 7:25 ` Simon Glass
2021-03-10 18:04 ` [PATCH 2/7] doc: FIT image: Introduce "u-boot,fpga-legacy" property Alexandru Gagniuc
2021-03-10 18:04 ` [PATCH 3/7] spl: fit: Move FPGA loading code to separate functions Alexandru Gagniuc
2021-03-15 7:25 ` Simon Glass
2021-03-10 18:04 ` [PATCH 4/7] spl: fit: Warn if FIT contains "fpga" property in config node Alexandru Gagniuc
2021-03-18 6:44 ` Simon Glass
2021-03-19 14:53 ` Alex G.
2021-03-19 23:54 ` Simon Glass
2021-03-10 18:04 ` [PATCH 5/7] spl: fit: Support loading FPGA images from list of "loadables" Alexandru Gagniuc
2021-03-29 7:43 ` Simon Glass
2021-03-29 15:35 ` Alex G.
2021-03-10 18:04 ` [PATCH 6/7] Kconfig: Document the limitations of the simple SPL_LOAD_FIT path Alexandru Gagniuc
2021-03-29 7:43 ` Simon Glass
2021-03-10 18:04 ` [PATCH 7/7] doc: FIT image: Update FPGA example to make use of "loadables" Alexandru Gagniuc
2021-03-29 7:43 ` Simon Glass
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=20210310180442.746517-1-mr.nuke.me@gmail.com \
--to=mr.nuke.me@gmail.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