From: gowtham.sureshkumar@arm.com
To: meta-arm@lists.yoctoproject.org, Ross.Burton@arm.com
Cc: nd@arm.com, Gowtham Suresh Kumar <gowtham.sureshkumar@arm.com>
Subject: [PATCH 0/2] Update UEFI capsule generation to use json config file
Date: Wed, 15 Feb 2023 10:42:34 +0000 [thread overview]
Message-ID: <20230215104236.24484-1-gowtham.sureshkumar@arm.com> (raw)
From: Gowtham Suresh Kumar <gowtham.sureshkumar@arm.com>
The UEFI capsule parameters can be passed to the script using a json file
which is easily scalable when generating multiple capsules. Also the edk2
base tools recipe is made native only.
Gowtham Suresh Kumar (2):
arm/edk2-basetools: Convert edk2 basetools recipes to native only
arm-bsp/uefi_capsule: Use json file to pass capsule config
.../recipes-bsp/images/corstone1000-image.bb | 8 +++---
...rstone1000-image-capsule-update-image.json | 11 ++++++++
meta-arm/classes/uefi_capsule.bbclass | 27 ++++++++++++-------
...211.bb => edk2-basetools-native_202211.bb} | 6 ++---
4 files changed, 35 insertions(+), 17 deletions(-)
create mode 100644 meta-arm-bsp/recipes-bsp/images/files/corstone1000-image-capsule-update-image.json
rename meta-arm/recipes-devtools/edk2-basetools/{edk2-basetools_202211.bb => edk2-basetools-native_202211.bb} (92%)
--
2.17.1
next reply other threads:[~2023-02-15 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 10:42 gowtham.sureshkumar [this message]
2023-02-15 10:42 ` [PATCH 1/2] arm/edk2-basetools: Convert edk2 basetools recipes to native only gowtham.sureshkumar
2023-02-15 10:42 ` [PATCH 2/2] arm-bsp/uefi_capsule: Use json file to pass capsule config gowtham.sureshkumar
2023-02-15 12:23 ` [meta-arm] " Jose Quaresma
2023-02-15 12:44 ` Gowtham Suresh Kumar
2023-02-15 13:14 ` Jose Quaresma
2023-02-17 4:30 ` [PATCH 0/2] Update UEFI capsule generation to use json config file Jon Mason
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=20230215104236.24484-1-gowtham.sureshkumar@arm.com \
--to=gowtham.sureshkumar@arm.com \
--cc=Ross.Burton@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
/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).