Hi Leif,
Thanks for your reply. Some comments in-line
> Hi Sakar,
>
> On Thu, Feb 26, 2015 at 10:36:18AM +, sakar.ar...@freescale.com
> wrote:
> > I see that by and large, the contents of SoC and Board Packages (ARM
> based) in EDK2, are like this:
> >
> >
> > - Most drivers like mm
Hi Olivier and Andrew,
Thanks for your respective suggestions. Accordingly I checked out my code and
found out that:
1. I checked the relevant stuff in the DSC and FDF files and I have the
following entries related to ConOut and ConIn:
MdeModulePkg/Universal/Console/ConPlatformDxe/ConPlatfo
acro or debugger to trace your execution.
> Try to understand why ConSplitterDxe does not set gST->ConIn and gST-
> >ConOut might a good starting point.
>
> > -Original Message-
> > From: bhupesh.sha...@freescale.com
> > [mailto:bhupesh.sha...
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
s
> execute state to aarch64.if this assumption exist, uefi bootloader just
> keep aarch32 state.
>
> Best wishes,
> -邮件原件-
> 发件人: bhupesh.sha...@freescale.com
> [mailto:bhupesh.sha...@freescale.com]
> 发送时间: 2014年1月13日 11:26
> 收件人: 'edk2-devel@lists.sourcef
relationship between arm-trusted-firmware and aarch64
> uefi boot code.
> Arm-trusted-firmware will load aarch64 uefi boot code and jump to run
> it?
>
> Best wishes,
> -邮件原件-
> 发件人: bhupesh.sha...@freescale.com
> [mailto:bhupesh.sha...@freescale.com]
> 发送时
Hi Olivier,
Thanks for your email.
I have one doubt. The various members of the ARMv7 family are different
architecturally - for e.g. Cortex-A7 can support LPAE while Cortex-A9 can't.
In such a case, how does a common ARMv7 library cater to all the architecture
variants? Are there specific lib
Hi,
The latest edk2/ArmPlatformPkg/Bds/Bds.inf puts NetLib as a required Library
class.
Some ARM based platforms (including ours) uses ArmPlatformPkg/Bds as the Boot
Device Selection source.
However, for such platforms, NetLib support can sometimes be optional for the
BDS stage,
causing compi
Hi,
The current AARCH64 UEFI is designed to run entirely in EL2 with the assumption
that the ARM Trusted FW (ATF) running in EL3 and launching
UEFI in EL2.
As a result if we try to use the UEFI bootloader as a bare-metal debug tool
(w/o the ATF, BootROM and so on..), we get an assertion failure
