public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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 4/5] OvmfPkg/README: document 4MB flash layout
Date: Fri, 19 May 2017 00:13:42 +0200	[thread overview]
Message-ID: <a701acbe-536d-51ec-4225-1e48a49cf836@redhat.com> (raw)
In-Reply-To: <20170518151436.16566-5-lersek@redhat.com>

On 05/18/17 17:14, Laszlo Ersek wrote:
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=527
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
> 
> Notes:
>     v2:
>     - no changes
> 
>  OvmfPkg/README | 39 ++++++++++++++++----
>  1 file changed, 31 insertions(+), 8 deletions(-)
> 
> diff --git a/OvmfPkg/README b/OvmfPkg/README
> index 304e69fbe545..33ff9432bb3e 100644
> --- a/OvmfPkg/README
> +++ b/OvmfPkg/README
> @@ -245,15 +245,20 @@ longer.)
>  
>  === OVMF Flash Layout ===
>  
> -Like all current IA32/X64 system designs, OVMF's firmware
> -device (rom/flash) appears in QEMU's physical address space
> -just below 4GB (0x100000000).
> +Like all current IA32/X64 system designs, OVMF's firmware device (rom/flash)
> +appears in QEMU's physical address space just below 4GB (0x100000000).
>  
> -The layout of the firmware device in memory looks like:
> +OVMF supports building a 1MB, 2MB or 4MB flash image (see the DSC files for the
> +FD_SIZE_1MB, FD_SIZE_2MB, FD_SIZE_4MB build defines). The base address for the
> +1MB image in QEMU physical memory is 0xfff00000. The base address for the 2MB
> +image is 0xffe00000. The base address for the 4MB image is 0xffc00000.
> +
> +Using the 1MB or 2MB image, the layout of the firmware device in memory looks
> +like:
>  
>  +--------------------------------------- 4GB (0x100000000)
>  | VTF0 (16-bit reset code) and OVMF SEC
> -| (SECFV)
> +| (SECFV, 208KB/0x34000)
>  +--------------------------------------- varies based on flash size
>  |
>  | Compressed main firmware image
> @@ -271,9 +276,27 @@ The layout of the firmware device in memory looks like:
>  | area (56KB/0xe000)
>  +--------------------------------------- base address
>  
> -OVMF supports building a 1MB or a 2MB flash image. The base address for
> -a 1MB image in QEMU physical memory is 0xfff00000. The base address for
> -a 2MB image is 0xffe00000.
> +Using the 4MB image, the layout of the firmware device in memory looks like:
> +
> ++--------------------------------------- base + 0x400000 (4GB/0x100000000)
> +| VTF0 (16-bit reset code) and OVMF SEC
> +| (SECFV, 208KB/0x34000)
> ++--------------------------------------- base + 0x3cc000
> +|
> +| Compressed main firmware image
> +| (FVMAIN_COMPACT, 3360KB/0x348000)
> +|
> ++--------------------------------------- base + 0x84000
> +| Fault-tolerant write (FTW)
> +| Spare blocks (264KB/0x42000)
> ++--------------------------------------- base + 0x42000
> +| FTW Work block (4KB/0x1000)
> ++--------------------------------------- base + 0x41000
> +| Event log area (4KB/0x1000)
> ++--------------------------------------- base + 0x40000
> +| Non-volatile variable storage
> +| area (256KB/0x40000)
> ++--------------------------------------- base address (0xffc00000)
>  
>  The code in SECFV locates FVMAIN_COMPACT, and decompresses the
>  main firmware (MAINFV) into RAM memory at address 0x800000. The
> 

Commit f78c8bf2c64f.


  reply	other threads:[~2017-05-18 22:13 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 [this message]
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

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=a701acbe-536d-51ec-4225-1e48a49cf836@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