From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH edk2-platforms 2/2] Silicon/NorFlashSynQuacerLib: describe entire firmware region as FV
Date: Wed, 13 Jun 2018 09:19:01 +0200 [thread overview]
Message-ID: <CAKv+Gu8VkE0dzhzgrU8VeYfZ1mivWGLFdxxbGUmNs4OJvMCcRw@mail.gmail.com> (raw)
In-Reply-To: <20180612225919.kroissnk2tusdw76@bivouac.eciton.net>
On 13 June 2018 at 00:59, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Thu, Jun 07, 2018 at 05:08:18PM +0200, Ard Biesheuvel wrote:
>> In order to allow for more flexibility when updating parts of the
>> firmware via capsule update, expand the description of the code FV
>> to cover the entire 4 MB region at the base of the NOR flash.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>> Silicon/Socionext/SynQuacer/Library/NorFlashSynQuacerLib/NorFlashSynQuacer.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/Silicon/Socionext/SynQuacer/Library/NorFlashSynQuacerLib/NorFlashSynQuacer.c b/Silicon/Socionext/SynQuacer/Library/NorFlashSynQuacerLib/NorFlashSynQuacer.c
>> index 816d8ba33f8c..357082c3d903 100644
>> --- a/Silicon/Socionext/SynQuacer/Library/NorFlashSynQuacerLib/NorFlashSynQuacer.c
>> +++ b/Silicon/Socionext/SynQuacer/Library/NorFlashSynQuacerLib/NorFlashSynQuacer.c
>> @@ -23,8 +23,9 @@ STATIC NOR_FLASH_DESCRIPTION mNorFlashDevices[] = {
>> {
>> // UEFI code region
>> SYNQUACER_SPI_NOR_BASE, // device base
>> - FixedPcdGet64 (PcdFdBaseAddress), // region base
>> - FixedPcdGet32 (PcdFdSize), // region size
>> + SYNQUACER_SPI_NOR_BASE, // region base
>> + FixedPcdGet32 (PcdFlashNvStorageVariableBase) -
>> + SYNQUACER_SPI_NOR_BASE, // region size
>
> Could you define the size as a macro in Platform/MemoryMap.h?
>
The memory map currently only contains constant macros. I can add this
expression
FixedPcdGet32 (PcdFlashNvStorageVariableBase) - SYNQUACER_SPI_NOR_BASE
somewhere as a #define but I would prefer it to be elsewhere, given
that it is not a SoC constant set in stone.
next prev parent reply other threads:[~2018-06-13 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:08 [PATCH edk2-platforms 0/2] DeveloperBox: prepare for expanding the capsule payload Ard Biesheuvel
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 [this message]
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=CAKv+Gu8VkE0dzhzgrU8VeYfZ1mivWGLFdxxbGUmNs4OJvMCcRw@mail.gmail.com \
--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