From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Thomas Abraham <thomas.abraham@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Cc: Rebecca Cran <rebecca@bsdio.com>
Subject: [PATCH edk2-platforms 0/2] Platform/ARM/JunoPkg: Increase FV size and enable NOOPT build
Date: Tue, 11 Apr 2023 07:46:41 -0600 [thread overview]
Message-ID: <20230411134643.116380-1-rebecca@bsdio.com> (raw)
The current FV size of 996KB for the Juno platform is rather restrictive
nowadays: a NOOPT build can be made to fit, but when enabling HTTPS boot
the firmware size becomes far too large even with an optimized DEBUG build.
Since the size value is rather arbitrary, bump it to 2MB: a build with
HTTPS boot and dynamic framework pkg uses around 72%, giving plenty of
headroom for future growth.
Since the NOOPT build makes source-level debugging via Arm Development
Studio so much more useful, enable it in the .dsc file.
Rebecca Cran (2):
Platform/ARM/JunoPkg: Bump the FV size to 2MB
Platform/ARM/JunoPkg: Enable the NOOPT build
Platform/ARM/JunoPkg/ArmJuno.dsc | 2 +-
Platform/ARM/JunoPkg/ArmJuno.fdf | 15 +++++++++++----
2 files changed, 12 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-11 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 13:46 Rebecca Cran [this message]
2023-04-11 13:46 ` [PATCH edk2-platforms 1/2] Platform/ARM/JunoPkg: Bump the FV size to 2MB Rebecca Cran
2023-04-11 13:46 ` [PATCH edk2-platforms 2/2] Platform/ARM/JunoPkg: Enable the NOOPT build Rebecca Cran
2023-04-12 11:28 ` [PATCH edk2-platforms 0/2] Platform/ARM/JunoPkg: Increase FV size and enable " 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=20230411134643.116380-1-rebecca@bsdio.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