Removed passing VA_LIST and some assembly language compatability issues. Did not fix ReportStatusCode passing VA_LIST (non-ANSI C Code), and some of the assembler was not not ported and int 3 was inserted, as it likely is not needed.
signed-off-by: andrewfish
reviewed-by: lgao4
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12006 6f19259b-4bc3-4df7-8a09-765794883524
- Give an overview of the different possible boot phases on ARM platforms (using
EDK2 for the full boot story or limiting its use to the last boot sequence)
- Show which functions to implement in ArmPlatformLib following the the boot phases
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12004 6f19259b-4bc3-4df7-8a09-765794883524
To build the UEFI BeagleBoard firmware using this ARM framework either use ./build-next.sh
or directly call the EDK2 BaseTools with BeagleBoardPkg-next.dsc.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11998 6f19259b-4bc3-4df7-8a09-765794883524
By setting this macro, the OMAP353x header is stripped from the UEFI firmware.
Some boot loader (eg: x-loader) loads the second stage boot loader (u-boot or
uefi) to a specific address and start the firmware from this address.
This macro ensures the reset vector is located at the beginning of the image.
To build the BeagleBoard with ./build.sh to enable this feature:
./build.sh -D EDK2_SECOND_STAGE_BOOTOLADER=1
Note: in this case, you must use BEAGLEBOARD_EFI.fd (and not
BeagleBoard_EFI_flashboot.fd)
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11995 6f19259b-4bc3-4df7-8a09-765794883524
In the former memory model, the UEFI firmware was expected to be located
at the top of the system memory. Stacks & Pi memory regions were set below
the firmware.
On some platform, the UEFI firmware could be shadowed by the ROM firmware
(case of the BeagleBoard) and in some cases the firmware is copied at the
beginning of the system memory.
With this new memory model, stack and Pi/DXE memory regions are set at the
top of the system memory wherever the UEFI firmware is located in the memory
map.
Because DXE core does not support shadowed firmwares, the system memory covered
by the UEFI firmware is marked as 'Non Present' to avoid to be overlapped by
DXE allocations.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11992 6f19259b-4bc3-4df7-8a09-765794883524
The PcdStandalone is a PCD ARM Ltd uses to make the difference between a standalone UEFI (boot
from cold boot to Boot Manager without user intervention) and a Debug UEFI firmware (the firmware
engineer has to copy the Normale World image into the DRAM to enable his/her firmware).
By coping the firmware into DRAM in the non standalone version it is much faster than reflashing
the NOR Flash after each build.
ArmPlatformSecExtraAction() function is called just before the Sec module jump to normal world.
The platform firmware can run extra actions at this stage.
The 'ARM Standalone' concept has moved to the implementation of ArmPlatformSecExtraAction() for
the ARM development boards (in ArmPlatformPkg/Library/DebugSecExtraActionLib).
ArmPlatformPkg: Enable DebugAgentLib in Sec and PrePeiCore
ArmPlatformPkg: Fix line endings in some source files
Use CR+LF line endings as defined by the EDK2 coding convention
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11991 6f19259b-4bc3-4df7-8a09-765794883524
This constructor should be explicitely called by the Sec or PrePi phase
to initialize the OMAP353x timers.
This function is a copy of the Timer initialization function in BeagleBoardPkg/Sec.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11988 6f19259b-4bc3-4df7-8a09-765794883524
BeagleBoardPkg: Switch to ArmPLatformPkg/Bds
The ArmPlatformPkg/Bds is able to boot Linux. Set the default boot device
for the BeagleBoardc to the SD card.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11971 6f19259b-4bc3-4df7-8a09-765794883524
If a FDT blob is passed to the kernel it is required we can load it.
If we fail to load the binary then we must abort the Linux booting
process.
ArmPkg/CpuDxe: Ensure the reset vector passed to the CP15 VBAR register is aligned on the right boundary
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11968 6f19259b-4bc3-4df7-8a09-765794883524
The $(BUILD_TARGETS) macro was used to make the difference between DEBUG and
RELEASE builds. The $(TARGET) macro should be used instead.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11961 6f19259b-4bc3-4df7-8a09-765794883524
When using ArmPlatformPkg/PrePeiCore or ArmPlatformPkg/PrePi, the global variable during
the XIP phase are stored on the top of the stack.
Global variables are defined by their PCD offset from the top of this stack.
For example, the HobListPtr is defined at the offset PcdHobListPtrGlobalOffset.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11958 6f19259b-4bc3-4df7-8a09-765794883524
andrewfish
jljusten
oliviermartin
jcarsey
niruiyu
ydong10
li-elvin
qianouyang
xdu2