From: Joel Stanley <joel@jms.id.au>
To: openbmc@lists.ozlabs.org, Eddie James <eajames@linux.ibm.com>,
Adriana Kobylak <anoo@us.ibm.com>
Cc: Andrew Jeffery <andrew@aj.id.au>
Subject: [PATCH u-boot v2019.04-aspeed-openbmc v2 0/2] Store default u-boot env in
Date: Mon, 21 Jun 2021 16:11:00 +0930 [thread overview]
Message-ID: <20210621064102.961633-1-joel@jms.id.au> (raw)
This patch adds the u-boot environment to the u-boot binary, and a build
fix for the new configuration that I have also sent upstream.
v2 uses the latest boot commands from openbmc.
We currently rely on the default environment being populated in the
image. This has the downside that if something corrupts the environment,
the system won't know how to boot itself.
The ast2600_openbmc_mmc.txt is copied from
meta-aspeed/recipes-bsp/u-boot/files/u-boot-env-ast2600.txt.
Adriana has indicated she will update openbmc to use the .txt from the
u-boot tree to generate the filesystem image (or we could stop doing
that, and simply use the default?).
Joel Stanley (2):
Makefile: Conditionally add defaultenv_h to envtools target
ast2600: Add environment for booting from mmc
Makefile | 2 ++
board/aspeed/ast2600_openbmc_mmc.txt | 11 +++++++++++
configs/ast2600_openbmc_spl_emmc_defconfig | 2 ++
3 files changed, 15 insertions(+)
create mode 100644 board/aspeed/ast2600_openbmc_mmc.txt
--
2.32.0
next reply other threads:[~2021-06-21 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 6:41 Joel Stanley [this message]
2021-06-21 6:41 ` [PATCH u-boot v2019.04-aspeed-openbmc v2 1/2] Makefile: Conditionally add defaultenv_h to envtools target Joel Stanley
2021-06-21 6:41 ` [PATCH u-boot v2019.04-aspeed-openbmc v2 2/2] ast2600: Add environment for booting from mmc Joel Stanley
2021-07-08 10:26 ` [PATCH u-boot v2019.04-aspeed-openbmc v2 0/2] Store default u-boot env in Graeme Gregory
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=20210621064102.961633-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=anoo@us.ibm.com \
--cc=eajames@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).