public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: 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>
Subject: Re: [PATCH edk2-platforms 0/2] Platform/ARM/JunoPkg: Increase FV size and enable NOOPT build
Date: Wed, 12 Apr 2023 13:28:22 +0200	[thread overview]
Message-ID: <CAMj1kXH8d+WPpKs_c2B+tfdYy+_y9F8XaG_RC=doyafduO=WmA@mail.gmail.com> (raw)
In-Reply-To: <20230411134643.116380-1-rebecca@bsdio.com>

On Tue, 11 Apr 2023 at 15:46, Rebecca Cran <rebecca@bsdio.com> wrote:
>
> 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
>

Thanks

Pushed as df82411375c5..9ca87c716f8a

      parent reply	other threads:[~2023-04-12 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:46 [PATCH edk2-platforms 0/2] Platform/ARM/JunoPkg: Increase FV size and enable NOOPT build Rebecca Cran
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 ` Ard Biesheuvel [this message]

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='CAMj1kXH8d+WPpKs_c2B+tfdYy+_y9F8XaG_RC=doyafduO=WmA@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