From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] xilinx: Enable redundant variables for all Xilinx SoCs
Date: Tue, 30 Mar 2021 12:09:56 +0200 [thread overview]
Message-ID: <cover.1617098995.git.michal.simek@xilinx.com> (raw)
Hi,
based on discussion with Tom here
https://lists.denx.de/pipermail/u-boot/2021-January/437234.html
I decided to enable redundant variables on all Xilinx SoCs. Users who don't
want to use it can disable this option. But having extended structure for
variable storing is based on that thread above the right way to go.
It means switch to the right approach is better to do earlier rather than
later.
Thanks,
Michal
Ashok Reddy Soma (2):
xilinx: zynq: Add support for saving env based on bootmode
xilinx: versal: Add support for saving env based on bootmode
Michal Simek (2):
env: Setup default value for ENV_OFFSET_REDUND
xilinx: Enable redundant variable handling
board/xilinx/versal/board.c | 30 ++++++++++++++++++++++++++
board/xilinx/zynq/board.c | 32 ++++++++++++++++++++++++++++
configs/microblaze-generic_defconfig | 1 +
configs/xilinx_versal_virt_defconfig | 4 ++++
configs/xilinx_zynq_virt_defconfig | 6 +++++-
configs/xilinx_zynqmp_virt_defconfig | 1 +
env/Kconfig | 3 ++-
7 files changed, 75 insertions(+), 2 deletions(-)
--
2.31.0
next reply other threads:[~2021-03-30 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 10:09 Michal Simek [this message]
2021-03-30 10:09 ` [PATCH 1/4] env: Setup default value for ENV_OFFSET_REDUND Michal Simek
2021-03-30 10:09 ` [PATCH 2/4] xilinx: zynq: Add support for saving env based on bootmode Michal Simek
2021-03-30 10:09 ` [PATCH 3/4] xilinx: versal: " Michal Simek
2021-03-30 10:10 ` [PATCH 4/4] xilinx: Enable redundant variable handling Michal Simek
2021-04-23 6:42 ` [PATCH 0/4] xilinx: Enable redundant variables for all Xilinx SoCs Michal Simek
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.1617098995.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.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