From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [PATCH v2 5/5] OvmfPkg: make the 4MB flash size the default (again)
Date: Tue, 23 May 2017 18:05:24 +0200 [thread overview]
Message-ID: <d327e563-c89a-de28-ae75-db629722c70a@redhat.com> (raw)
In-Reply-To: <20170518151436.16566-6-lersek@redhat.com>
On 05/18/17 17:14, Laszlo Ersek wrote:
> The previously default 2MB can be explicitly selected with
>
> -D FD_SIZE_2MB
>
> or
>
> -D FD_SIZE_IN_KB=2048
>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Suggested-by: Jordan Justen <jordan.l.justen@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> (cherry picked from commit bba8dfbec3bbc4fba7fa6398ba3cf76593e0725e)
> ---
>
> Notes:
> v2:
> - no changes
> - we can postpone this one patch if we want to wait for Xen to update
> hvmloader
>
> OvmfPkg/OvmfPkgIa32.dsc | 2 +-
> OvmfPkg/OvmfPkgIa32X64.dsc | 2 +-
> OvmfPkg/OvmfPkgX64.dsc | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc
> index bd115c9ced93..8f0ab9f721fe 100644
> --- a/OvmfPkg/OvmfPkgIa32.dsc
> +++ b/OvmfPkg/OvmfPkgIa32.dsc
> @@ -54,7 +54,7 @@ [Defines]
> !ifdef $(FD_SIZE_4MB)
> DEFINE FD_SIZE_IN_KB = 4096
> !else
> - DEFINE FD_SIZE_IN_KB = 2048
> + DEFINE FD_SIZE_IN_KB = 4096
> !endif
> !endif
> !endif
> diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc b/OvmfPkg/OvmfPkgIa32X64.dsc
> index 9727db842922..4b2136262865 100644
> --- a/OvmfPkg/OvmfPkgIa32X64.dsc
> +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
> @@ -54,7 +54,7 @@ [Defines]
> !ifdef $(FD_SIZE_4MB)
> DEFINE FD_SIZE_IN_KB = 4096
> !else
> - DEFINE FD_SIZE_IN_KB = 2048
> + DEFINE FD_SIZE_IN_KB = 4096
> !endif
> !endif
> !endif
> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc
> index 61aaed761657..2ee30fb00a28 100644
> --- a/OvmfPkg/OvmfPkgX64.dsc
> +++ b/OvmfPkg/OvmfPkgX64.dsc
> @@ -54,7 +54,7 @@ [Defines]
> !ifdef $(FD_SIZE_4MB)
> DEFINE FD_SIZE_IN_KB = 4096
> !else
> - DEFINE FD_SIZE_IN_KB = 2048
> + DEFINE FD_SIZE_IN_KB = 4096
> !endif
> !endif
> !endif
>
This patch has been now committed (completing the series); please refer
to <https://lists.01.org/pipermail/edk2-devel/2017-May/010911.html>.
Thanks
Laszlo
prev parent reply other threads:[~2017-05-23 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 15:14 [PATCH v2 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) Laszlo Ersek
2017-05-18 15:14 ` [PATCH v2 1/5] OvmfPkg/EmuVariableFvbRuntimeDxe: strip trailing whitespace Laszlo Ersek
2017-05-18 22:12 ` Laszlo Ersek
2017-05-18 15:14 ` [PATCH v2 2/5] OvmfPkg/EmuVariableFvbRuntimeDxe: change block size to 4KB Laszlo Ersek
2017-05-18 18:49 ` Jordan Justen
2017-05-18 19:40 ` Laszlo Ersek
2017-05-18 20:56 ` Jordan Justen
2017-05-18 21:09 ` Laszlo Ersek
2017-05-18 22:13 ` Laszlo Ersek
2017-05-18 15:14 ` [PATCH v2 3/5] OvmfPkg/PlatformPei: align EmuVariableNvStore at any page boundary Laszlo Ersek
2017-05-18 22:13 ` Laszlo Ersek
2017-05-18 15:14 ` [PATCH v2 4/5] OvmfPkg/README: document 4MB flash layout Laszlo Ersek
2017-05-18 22:13 ` Laszlo Ersek
2017-05-18 15:14 ` [PATCH v2 5/5] OvmfPkg: make the 4MB flash size the default (again) Laszlo Ersek
2017-05-23 16:05 ` Laszlo Ersek [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=d327e563-c89a-de28-ae75-db629722c70a@redhat.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