4d2ea2616e
The relocatable build of ArmVirtQemuKernel is designed to be executed from RAM, and contains some scratch memory at the start of the image to use as a stack very early on, and to preserve the DTB image received from QEMU while it discovers and initializes memory. It turns out that 8 KB is a bit on the small side here, especially when executing with secure world emulation enabled, in which case there are additional nodes present. So increase the slack space to 32 KB. While at it, remove a stale Xen reference that was copy/pasted when this file was created. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Acked-by: Laszlo Ersek <lersek@redhat.com>
136 lines
5.1 KiB
Plaintext
136 lines
5.1 KiB
Plaintext
#
|
|
# Copyright (c) 2011-2015, ARM Limited. All rights reserved.
|
|
# Copyright (c) 2014, Linaro Limited. All rights reserved.
|
|
# Copyright (c) 2015 - 2016, Intel Corporation. All rights reserved.
|
|
#
|
|
# This program and the accompanying materials
|
|
# are licensed and made available under the terms and conditions of the BSD License
|
|
# which accompanies this distribution. The full text of the license may be found at
|
|
# http://opensource.org/licenses/bsd-license.php
|
|
#
|
|
# THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
|
|
#
|
|
|
|
################################################################################
|
|
#
|
|
# FD Section
|
|
# The [FD] Section is made up of the definition statements and a
|
|
# description of what goes into the Flash Device Image. Each FD section
|
|
# defines one flash "device" image. A flash device image may be one of
|
|
# the following: Removable media bootable image (like a boot floppy
|
|
# image,) an Option ROM image (that would be "flashed" into an add-in
|
|
# card,) a System "Flash" image (that would be burned into a system's
|
|
# flash) or an Update ("Capsule") image that will be used to update and
|
|
# existing system flash.
|
|
#
|
|
################################################################################
|
|
|
|
[FD.QEMU_EFI]
|
|
BaseAddress = 0x00000000|gArmTokenSpaceGuid.PcdFdBaseAddress # QEMU assigns 0 - 0x8000000 for a BootROM
|
|
Size = 0x00200000|gArmTokenSpaceGuid.PcdFdSize # The size in bytes of the FLASH Device
|
|
ErasePolarity = 1
|
|
|
|
# This one is tricky, it must be: BlockSize * NumBlocks = Size
|
|
BlockSize = 0x00001000
|
|
NumBlocks = 0x200
|
|
|
|
################################################################################
|
|
#
|
|
# Following are lists of FD Region layout which correspond to the locations of different
|
|
# images within the flash device.
|
|
#
|
|
# Regions must be defined in ascending order and may not overlap.
|
|
#
|
|
# A Layout Region start with a eight digit hex offset (leading "0x" required) followed by
|
|
# the pipe "|" character, followed by the size of the region, also in hex with the leading
|
|
# "0x" characters. Like:
|
|
# Offset|Size
|
|
# PcdOffsetCName|PcdSizeCName
|
|
# RegionType <FV, DATA, or FILE>
|
|
#
|
|
################################################################################
|
|
|
|
#
|
|
# Implement the Linux kernel header layout so that the loader will identify
|
|
# it as something bootable, and execute it with a FDT pointer in x0 or r2.
|
|
# This area will be reused to store a copy of the FDT so round it up to 32 KB.
|
|
#
|
|
0x00000000|0x00008000
|
|
DATA = {
|
|
!if $(ARCH) == AARCH64
|
|
0x01, 0x00, 0x00, 0x10, # code0: adr x1, .
|
|
0xff, 0x1f, 0x00, 0x14, # code1: b 0x8000
|
|
0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, # text_offset: 512 KB
|
|
0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, # image_size: 2 MB
|
|
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # flags
|
|
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res2
|
|
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res3
|
|
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res4
|
|
0x41, 0x52, 0x4d, 0x64, # magic: "ARM\x64"
|
|
0x00, 0x00, 0x00, 0x00 # res5
|
|
!else
|
|
0x08, 0x10, 0x4f, 0xe2, # adr r1, .
|
|
0x02, 0x00, 0xa0, 0xe1, # mov r0, r2 (DTB)
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
0x00, 0x00, 0xa0, 0xe1, # nop
|
|
|
|
0xf6, 0x1f, 0x00, 0xea, # b 0x8000
|
|
0x18, 0x28, 0x6f, 0x01, # magic
|
|
0x00, 0x00, 0x00, 0x00, # start
|
|
0x00, 0x00, 0x20, 0x00, # image size: 2 MB
|
|
0x01, 0x02, 0x03, 0x04 # endiannness flag
|
|
!endif
|
|
}
|
|
|
|
0x00008000|0x001f8000
|
|
gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize
|
|
FV = FVMAIN_COMPACT
|
|
|
|
!include VarStore.fdf.inc
|
|
|
|
################################################################################
|
|
#
|
|
# FV Section
|
|
#
|
|
# [FV] section is used to define what components or modules are placed within a flash
|
|
# device file. This section also defines order the components and modules are positioned
|
|
# within the image. The [FV] section consists of define statements, set statements and
|
|
# module statements.
|
|
#
|
|
################################################################################
|
|
|
|
!include ArmVirtQemuFvMain.fdf.inc
|
|
|
|
[FV.FVMAIN_COMPACT]
|
|
FvAlignment = 16
|
|
ERASE_POLARITY = 1
|
|
MEMORY_MAPPED = TRUE
|
|
STICKY_WRITE = TRUE
|
|
LOCK_CAP = TRUE
|
|
LOCK_STATUS = TRUE
|
|
WRITE_DISABLED_CAP = TRUE
|
|
WRITE_ENABLED_CAP = TRUE
|
|
WRITE_STATUS = TRUE
|
|
WRITE_LOCK_CAP = TRUE
|
|
WRITE_LOCK_STATUS = TRUE
|
|
READ_DISABLED_CAP = TRUE
|
|
READ_ENABLED_CAP = TRUE
|
|
READ_STATUS = TRUE
|
|
READ_LOCK_CAP = TRUE
|
|
READ_LOCK_STATUS = TRUE
|
|
|
|
INF ArmVirtPkg/PrePi/ArmVirtPrePiUniCoreRelocatable.inf
|
|
|
|
FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {
|
|
SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {
|
|
SECTION FV_IMAGE = FVMAIN
|
|
}
|
|
}
|
|
|
|
!include ArmVirtRules.fdf.inc
|