From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Devon Bautista <dbautista@newmexicoconsortium.org>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH v2 1/1] OvmfPkg: Introduce 16MiB flash size for (primarily) Linuxboot
Date: Fri, 3 Sep 2021 09:17:22 +0200 [thread overview]
Message-ID: <20210903071722.ebm4vc4tzsa3sdlu@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210903052620.30638-2-dbautista@newmexicoconsortium.org>
On Fri, Sep 03, 2021 at 05:26:20AM +0000, Devon Bautista wrote:
> The largest size flash image currently available for OVMF builds, 4MiB,
> is too small to insert a Linux kernel and initramfs into the DXEFV, and
> is thus insufficient for testing Linuxboot builds via OVMF.
> FVMAIN_COMPACT uncompressed 3360 -> 15648 (+12288)
> FV FFS file LZMA compressed
> PEIFV uncompressed 896 -> 896 ( +0)
> individual PEI uncompressed
> modules
> DXEFV uncompressed 12288 -> 12288 ( +0)
> individual DXE uncompressed
> modules
Patch looks sane to me.
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
How you are going to use the extra space you got?
Do you add kernel + initrd as ffs files to FVMAIN_COMPACT?
take care,
Gerd
next prev parent reply other threads:[~2021-09-03 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 5:26 [PATCH v2 0/1] OVMF: Introduce 16MiB Flash Size Devon Bautista
2021-09-03 5:26 ` [PATCH v2 1/1] OvmfPkg: Introduce 16MiB flash size for (primarily) Linuxboot Devon Bautista
2021-09-03 7:17 ` Gerd Hoffmann [this message]
2021-09-03 19:35 ` Devon Bautista
2021-09-06 8:37 ` Gerd Hoffmann
2021-09-07 0:55 ` Devon Bautista
2021-09-09 9:09 ` [edk2-devel] " Philippe Mathieu-Daudé
2021-09-09 12:10 ` Gerd Hoffmann
2021-10-19 23:03 ` Devon Bautista
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=20210903071722.ebm4vc4tzsa3sdlu@sirius.home.kraxel.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