Re: [edk2] TrustZone support for VE Cortex A15?

Yes, I use RTSM VE A15x2. I do not have real hardware, but I use the Fast Model simulator. By now I have read in the specs of arm.com that the Cortex-A15 test chip does not have TZ support. I was surprised, because the Cortex-A15 is v7 and supports the virtualization extensions, so according to

Re: [edk2] TrustZone support for VE Cortex A15?

To be more precise, I use ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-A15_MPCore.dsc to build the UEFI boot loader. This is from the tianocore EDK2 SVN repository. I run this on the Fast Model simulator, simulating a examples/RTSM_VE/Build_Cortex-A15x2 board. My DTB is compiled from http:/

Re: [edk2] Boot Linux on ARM: how to pass in FDT?

BTW the kernel boots if I compile it with CONFIG_ARM_APPENDED_DTB=y and then do a cat vexpress.dtb zImage > zImage.fdt and then use zImage.fdt as kernel to boot. So I'm quite sure the problem must be in the Bds code of the UEFI boot loader. It does not seem to be able to parse the DTB properly.

Re: [edk2] TrustZone support for VE Cortex A15?

As you have a workaround, I will investigate the Linux boot issue later. But you are right it looks to be a problem in the Bds. To answer your previous email, Cortex A15 has Security Extension and Virtualization Extension. So you can switch from Secure to Non-Secure World and use SMC (Secure Monito

[edk2] Issue - 'ifconfig -c' not clearing IP address details

Hello EDK2 Developers, Am facing some issues while clearing the IP address details through shell, am using "ifconfig -c" to clear the previously acquired DHCP address but it acquires the IP address again within a second. Below are the steps I followed with the behavior within braces:- 1. Boot

Re: [edk2] xen OVMF problem

Hi, Bei, Thanks a lot! I have tried it with the ovmf.bin which you provided, and I get the boot info: 16 32 b1 f1 64 SecCoreStartupWithStack(0xFFFE6000, 0x8) File->Type: 0xB Section->Type: 0x2 Section->Type: 0x19 Section->Type (0x19) != SectionType (0x17) Section->Type: 0x17 File->Type: 0x2 Fi

Re: [edk2] [PATCH] OvmfPkg VirtioScsiDxe: Fix build with VS2010

On 10/22/12 23:42, Jordan Justen wrote: > Structures should not be directly assigned in EDK II > code, since this leads to different behaviours on various > compilers. > > Instead, use ZeroMem to zero out the structures. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by:

[edk2] UnicodeVSPrint returns nonsense string length

Greeting, UnicodeVSPrint is not returning the correct (expected) string length. The simple program below demonstrates the problem. The build environment is UDK2010.SR1.UP1. This demo was built as a module in MdeModulePkg. When the demo program is run the output is: fooprint:Count: 6 Count = 6 foo

Re: [edk2] xen OVMF problem

2012/10/23 Gonglei (Arei) > Hi, Bei, > > Thanks a lot! > > I have tried it with the ovmf.bin which you provided, and I get the boot > info: > > ** ** > > 16 > > 32 > > b1 > > f1 > > 64 > > SecCoreStartupWithStack(0xFFFE6000, 0x8) > > File->Type: 0xB >

Re: [edk2] xen OVMF problem

On Tue, Oct 23, 2012 at 4:42 AM, Gonglei (Arei) wrote: > /home/sdb2/arei/xen-upgrade/xen-4.2.0.bak/tools/firmware/ovmf/MdePkg/Library/PeiMemoryAllocationLib/MemoryAllocationLib.c:713: > error: 'ms_abi' attribute directive ignored Ah! This could certainly explain things. Does '/usr/bin/gcc -v' re

Re: [edk2] xen OVMF problem

On 10/23/12 17:38, Bei Guan wrote: > > > 2012/10/23 Gonglei (Arei) > > > I delete “-DEFIAPI=__attribute__((sysv_abi))”so that the ovmf can > be built successfully in the ovmf/Conf/tools_def.txt: > > DEFINE GCC44_X64_CC_FLAGS= DEF(GC

[edk2] Shoulnd't vars Boot#### be UpperCase?

Hi, seems that in edk2 implementation of efi there is a small violation of EFI-spec. The UEFI_2_3_1_Errata_C_final.pdf, section "3.1.1 Boot Manager Programming" says "Each load option entry resides in a Boot variable or a Driver variable where the is replaced by a unique option nu

Re: [edk2] Shoulnd't vars Boot#### be UpperCase?

You would be right if you were using printf. However, in PrintLibInternal.c (MdePkg/Library/BasePrintLib), line 20 and then lines 523ff, you can see that all hex numbers are converted to upper case whether using ‘x’ or ‘X’ Tim From: Dmitriy Skorodumov [mailto:dsk...@mail.ru] Sent: Tuesday, Oct

Re: [edk2] New to EFI. help needed

Thanks Daryl, To answer to your question : In what way does it not work? What symptoms or error messages do you get? I do not get any error messages. I simply get a prompt when I try to execute python scripts. And I downloaded EADK Alpha2.zip from the given link to get the AppPkg,StdLib an

Re: [edk2] UnicodeVSPrint returns nonsense string length

On Tue, Oct 23, 2012 at 5:43 AM, duck wilson wrote: > UnicodeVSPrint is not returning the correct (expected) string length. The > simple program below demonstrates > the problem. The build environment is UDK2010.SR1.UP1. This demo was built > as a module in MdeModulePkg. > When the demo program is

[edk2] Both legacy OpROM and UEFI BSD loaded

Hello All, In our add-on controllers we flash both UEFI and Legacy OptionROM images and we have seen in some platforms both legacy OpROM and UEFI BSD are loaded by the UEFI system firmware. Is it acceptable case and if so do the system firmware can have the possibility of executing either of the

[edk2] edk2.svn.sourceforge.net down?

I'm getting errors from SVN... Cameron Esfahani di...@apple.com "I cannot for the life of me understand why, while people without driver's licenses are not allowed on public roads, in bookstores one can find any number of books by persons without decency - let alone knowledge." "His Master's V

Re: [edk2] UnicodeVSPrint returns nonsense string length

Thanks MUCH Jordan! Adding EFIAPI to the function declararion solved the problem as in, UINTN EFIAPI fooprint ( IN CONST CHAR16 *Format, ... ) I inherited a mixture of working EDK production code and some working, and some not, EDK2 code. This problem arose in some code ported from EDK to

Re: [edk2] xen OVMF problem

Hi Jordan, Laszlo, Bei Thanks for your help! My compiler is gcc-4.3.4 linux-aVzzFl:~ # /usr/bin/gcc -v Using built-in specs. Target: x86_64 -linux Thread model: posix gcc version 4.3.4 [gcc-4_3-branch revision 152973] Next, As your says, I will try it with higher GCC. Best Regards! Arei