From: "Richard Lyu via groups.io" <richard.lyu=suse.com@groups.io>
To: kraxel@redhat.com, devel@edk2.groups.io
Subject: Re: [edk2-devel] [OvmfPkg] Build fails due to insufficient FV size in edk2-stable202502
Date: Wed, 12 Mar 2025 13:44:42 +0800 [thread overview]
Message-ID: <Z9EfSiEr2rnBN4E7@localhost.localdomain> (raw)
In-Reply-To: <gd6gz3gs5otb2wzlltivafnujrly2atch6tn4vdhzf672tl3kp@gaa4o52jsrjc>
Hi Gerd,
I will also try this method. Thank you for your suggestions.
Best Regards
Richard Lyu
On 2025/03/11 13:14, Gerd Hoffmann wrote:
> On Tue, Mar 11, 2025 at 03:16:29PM +0800, Richard Lyu via groups.io wrote:
> > Hi memristor2, ardb,
> >
> > Thank you for your suggestions, but since there is a requirement to use a 2MB size, I need to maintain the size at FD_SIZE_2MB. So, is there any other way to reduce the size, such as by modifying the fdf file?
> > Would this method be worth trying?
>
> There are a bunch of options you can set via -D to exclude some
> features, for example NETWORK_ISCSI_ENABLE=FALSE turns off iscsi
> support, or NETWORK_TLS_ENABLE=FALSE turns of TLS (https) support.
>
> HTH,
> Gerd
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121187): https://edk2.groups.io/g/devel/message/121187
Mute This Topic: https://groups.io/mt/111635652/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-03-12 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 6:45 [edk2-devel] [OvmfPkg] Build fails due to insufficient FV size in edk2-stable202502 Richard Lyu via groups.io
2025-03-11 6:54 ` memristor2 via groups.io
2025-03-11 7:03 ` Ard Biesheuvel via groups.io
2025-03-11 7:16 ` Richard Lyu via groups.io
2025-03-11 7:30 ` memristor2 via groups.io
2025-03-11 7:47 ` Richard Lyu via groups.io
2025-03-11 12:14 ` Gerd Hoffmann via groups.io
2025-03-12 5:44 ` Richard Lyu via groups.io [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=Z9EfSiEr2rnBN4E7@localhost.localdomain \
--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