On Fri, Jan 10, 2014 at 9:26 PM, Laszlo Ersek wrote:
> The Linux persistent store (pstore) feature serves, among other things,
> for saving the trailing portion of the dmesg in case of a kernel oops. One
> backend for the pstore facility is "efivars", ie. non-volatile UEFI
> variables.
>
> Linux s
Hi, sharma:
Thank you very much!
I got it:
Arm-trusted-firmware is the first running code on Foundation model.
It runs at aarch64 execution state.
Best wishes,
-邮件原件-
发件人: bhupesh.sha...@freescale.com [mailto:bhupesh.sha...@freescale.com]
发送时间: 2014年1月13日 12:48
收件人: 'edk2-devel@lists.so
Hi Tiger,
Yes, the Trusted firmware runs in EL3 and calls the UEFI boot firmware which
runs in EL2.
In the trusted firmware project
https://github.com/ARM-software/arm-trusted-firmware
you will find the instructions to launch UEFI from this firmware on the ARM
FVPs (fixed Virtual
Platforms) -
Hi, sharma:
I used arm-none-linux-gnueabi-gcc-4.5.2 to compile 32bit uefi code.
I have a question about foundation model:
1. There is an Open Source implementation of the Trusted/Secure Firmware:
https://github.com/ARM-software/arm-trusted-firmware
So, what is the relationship between ar
Hi Tiger,
You can use the AArch64 foundation model support code in the EDK2 code base to
write reference code for your ARMv8 SoC.
Also which toolchain do you use for compiling your AArch32 (32-bit code)?
Regards,
Bhupesh
> -Original Message-
> From: tiger...@viatech.com.cn [mailto:tig
Hi, sharma:
Thanks for your answer!
I described my understanding on current ARM UEFI code:
1. Most ARM UEFI code package is based on ARMv7 SOCs.
Because of lacking ARMv8 development board, so enthusiast ported uefi code
on 32bit SOC.
2. ARMv8 supports aarch32 state.
So, if ARMv8 SOC powere
Hi Tiger,
AFAIK, the AArch64 ISA is written from scratch for 64-bit support.
Although it is backward compatible with AArch32 and binaries compiled
for AArch32 (ARMv7 compatible) are supposed to run well on the ARMv8
machine running in AArch32 mode.
However, as per my understanding (and Olivier c
Reviewed-by: Ruiyu Ni
From: Carsey, Jaben
Sent: Saturday, January 11, 2014 1:10 AM
To: Ni, Ruiyu
Cc: edk2-devel@lists.sourceforge.net; Carsey, Jaben
Subject: ShellPkg: Fix command line parsing for script files (%1, %1, etc...)
Ray,
Can you verify this please?
ShellPkg: Fix command line pa
I would recommend you first check whether network drivers are correctly
connected.
Could you check the serial output when you type 'drivers' command?
Thanks,
Ruth
-Original Message-
From: Pawel Mazurek [mailto:ziur...@gmail.com]
Sent: Monday, January 13, 2014 9:07 AM
To: edk2-devel@list
Dear Ramesh,
I already tried LocateProtocol , but it doesn`t work.
This is my code, how can I fix it?
EFI_STATUS
EFIAPI
UefiMain (
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
)
{
CurDir = getCurrentDir(ImageHandle); <-- Call in UefiMain
}
CONST
CHAR1
Hello.
I got a problem while I try to run in emulator WebServer.efi from EDKII.
While I try to run the program i get this error message:
ERROR with Ip4 layer, Status: Not Found
ERROR with Tcp4 layer, Status: Not Found ERROR with Tcp6 layer, Status: Not
Found
ERROR with Udp4 layer, Status: Not F
Hi, Oliver:
I have a question abourt ARMv8 CPU's bootloader.
ARMv8 supports: AARCH32 / AARCH64
Take an example:
An ARMv8 SOC, when power up / reset, its default state is : AARCH32
Then, could i still run an old arm uefi bootloader which written by
ARMv7 instruction set?
I will switch ARMv8 SOC to A
By splitting the PEI and DXE phases into separate FVs,
we can only reserve the PEI FV for ACPI S3 support.
This should save about 7MB.
Unfortunately, this all has to happen in a single commit.
DEC:
* Remove PcdOvmfMemFv(Base|Size)
* Add PcdOvmfPeiMemFv(Base|Size)
* Add PcdOvmfDxeMemFv(Base|Size)
13 matches
Mail list logo
