From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: edk2-devel@lists.01.org
Cc: leif.lindholm@linaro.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH edk2-platforms 0/2] DeveloperBox: prepare for expanding the capsule payload
Date: Thu, 7 Jun 2018 17:08:16 +0200 [thread overview]
Message-ID: <20180607150818.14393-1-ard.biesheuvel@linaro.org> (raw)
We intend to start distributing firmware update capsules that include the SCP
firmware partition. In order to allow for more flexibility regarding whether
a capsule contains this piece or not, update the flash access routines and
the flash partition descriptions so we can update any part of the first
4 MB, consisting of the CM3 bootstrap code, emergency flasher, pseudo
EEPROM, SCP firmware, ARM-TF and UEFI.
Note that this means we can drop the 'TEMPORARY' patch I proposed a while
ago to hack around this limitation.
Ard Biesheuvel (2):
Silicon/SynQuacerPlatformFlashAccessLib: relax FV address check
Silicon/NorFlashSynQuacerLib: describe entire firmware region as FV
.../NorFlashSynQuacerLib/NorFlashSynQuacer.c | 5 +-
.../SynQuacerPlatformFlashAccessLib.c | 53 +++++++++----------
2 files changed, 28 insertions(+), 30 deletions(-)
--
2.17.0
next reply other threads:[~2018-06-07 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:08 Ard Biesheuvel [this message]
2018-06-07 15:08 ` [PATCH edk2-platforms 1/2] Silicon/SynQuacerPlatformFlashAccessLib: relax FV address check Ard Biesheuvel
2018-06-12 23:03 ` Leif Lindholm
2018-06-13 12:06 ` Ard Biesheuvel
2018-06-13 13:17 ` Leif Lindholm
2018-06-07 15:08 ` [PATCH edk2-platforms 2/2] Silicon/NorFlashSynQuacerLib: describe entire firmware region as FV Ard Biesheuvel
2018-06-12 22:59 ` Leif Lindholm
2018-06-13 7:19 ` Ard Biesheuvel
2018-06-13 10:00 ` Leif Lindholm
2018-06-13 12:00 ` Ard Biesheuvel
2018-06-13 12:28 ` Leif Lindholm
2018-06-07 16:06 ` [PATCH edk2-platforms 0/2] DeveloperBox: prepare for expanding the capsule payload Ard Biesheuvel
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-list 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=20180607150818.14393-1-ard.biesheuvel@linaro.org \
--to=devel@edk2.groups.io \
/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