From: Jerome Forissier <jerome.forissier@linaro.org>
To: u-boot@lists.denx.de
Cc: Jerome Forissier <jerome.forissier@linaro.org>,
Jagan Teki <jagan@amarulasolutions.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Heiko Schocher <hs@denx.de>,
Xavier Drudis Ferran <xdrudis@tinet.cat>,
Michal Simek <michal.simek@amd.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Nishanth Menon <nm@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>
Subject: [PATCH 0/2] spl, rk3399: fix FIT image loadingg out-of-range
Date: Thu, 9 Jun 2022 17:23:20 +0200 [thread overview]
Message-ID: <cover.1654787433.git.jerome.forissier@linaro.org> (raw)
The patches in this series address an issue I met when trying to enable
FIT signature verification by SPL on a RockPi4B board.
- The first patch avoids a buffer overflow when writing to INTMEM1 SRAM
- The second one addresses reliability issues I had with back-to-back
MMC reads from the microSD card. By allowing DMA operation, the issue is
gone and generally speaking DMA is preferred over FIFO mode anyways.
Jerome Forissier (2):
spl: fit: add config option for temporary buffer when loading image
rockchip: rk3399: enable spl-fifo-mode for sdmmc only when needed
arch/arm/dts/rk3399-u-boot.dtsi | 2 +
common/spl/Kconfig | 45 +++++++++++++++++++
common/spl/spl_fit.c | 79 ++++++++++++++++++++++++++++++---
3 files changed, 120 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2022-06-09 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:23 Jerome Forissier [this message]
2022-06-09 15:23 ` [PATCH 1/2] spl: fit: add config option for temporary buffer when loading image Jerome Forissier
2022-06-09 15:23 ` [PATCH 2/2] rockchip: rk3399: enable spl-fifo-mode for sdmmc only when needed Jerome Forissier
2022-06-14 18:16 ` Jerome Forissier
2022-06-15 17:05 ` Xavier Drudis Ferran
2022-06-29 3:01 ` Kever Yang
2022-06-29 7:59 ` Jerome Forissier
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=cover.1654787433.git.jerome.forissier@linaro.org \
--to=jerome.forissier@linaro.org \
--cc=a-govindraju@ti.com \
--cc=hs@denx.de \
--cc=jagan@amarulasolutions.com \
--cc=jh80.chung@samsung.com \
--cc=kever.yang@rock-chips.com \
--cc=lokeshvutla@ti.com \
--cc=michal.simek@amd.com \
--cc=mr.nuke.me@gmail.com \
--cc=nm@ti.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xdrudis@tinet.cat \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.