On 7 August 2015 at 22:15, Scott Duplichan wrote:
> Some gnu linkers used with GCC44, such as GNU ld 2.19.1, require a
> --defsym= command line option to precede the --script= option in
> order for the definition to be available for use by the script.
> Move the --defsym= command line option to sa
In InitializeConsolePipe (), we clobber the Status variable in the
error handling path that reports Status in its output. Instead,
use a NULL check on the LocateProtocol () output argument.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/L
This series adds support for using the Intel BDS with ArmVExpress-FVP,
and for building it with UEFI Secure Boot enabled.
Note that the former is a prerequisite of the latter, since the ARM BDS
has no GUI for enrolling certificates and enabling secure boot.
Patch #1 removes the PlatformIntelBdsLI
This allows the FVP target to be built with UEFI Secure Boot enabled,
by passing -D SECURE_BOOT_ENABLE to the build command line. Note that
you will need to disable the ARM BDS (-D USE_ARM_BDS=FALSE) or you will
not be able to enroll certificates, since the ARM BDS does not provide
a GUI to do so.
Add a call to EnableQuietBoot () to BdsPlatformPolicyBehavior(),
so that a splash screen is shown in case one is present under the
correct GUID in the FV, and we have graphics support.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/Librar
The Intel BDS platform library still depends on the ARM BDS specific
BdsLib. So replace its invocations with GenericBdsLib counterparts,
and fix up where needed, so that we can drop the dependency.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatf
This adds support for the Intel BDS, by introducing a define
'USE_ARM_BDS' which defaults to TRUE, and can be overridden on
the build command line.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-FVP-AArch64.dsc
On 08/08/15 08:13, Benjamin Herrenschmidt wrote:
> Hi !
>
> I'm still trying to get my head around the internals of EDK here so
> bear with me if there's an obvious answer that I missed ... :-)
>
> I'm trying to understand how I can properly reserve bits of memory
> from my PrePei or Pei so that DX
> On Aug 8, 2015, at 8:12 AM, Laszlo Ersek wrote:
>
> On 08/08/15 08:13, Benjamin Herrenschmidt wrote:
>> Hi !
>>
>> I'm still trying to get my head around the internals of EDK here so
>> bear with me if there's an obvious answer that I missed ... :-)
>>
>> I'm trying to understand how I can p
Does anyone tested network(ping/tftp) using E1000/NIC PCI card on Juno board?
Which LAN E1000 driver(source or any link) is used and tested for Intel NIC
card?
Thanks and Regards,
Shaveta
-Original Message-
From: Leekha Shaveta-B20052
Sent: Friday, August 07, 2015 10:59 AM
To: 'Ye, Ting
On Sat, 2015-08-08 at 17:12 +0200, Laszlo Ersek wrote:
> > What am I missing ? :-)
>
> I think you were missing the conceptual hierarchy between the GCD
> memory
> space map and the UEFI memory map, and which HOBs produced in PEI
> (resource vs. allocation), and which services called in DXE and la
On Sat, 2015-08-08 at 08:56 -0700, Andrew Fish wrote:
> If you really need to punch holes in the memory map, then you can use
> resource descriptors.
Yes, I do need to punch holes in there, Laszlo explanation (which I
haven't fully digested yet) implies that using allocation hobs should
work whic
On Sat, 2015-08-08 at 17:12 +0200, Laszlo Ersek wrote:
> If that's indeed your point, then maybe it will help to look at the call
> tree "context" in the DXE core, where this function --
> CoreInitializeMemoryServices() -- is called from:
>
> DxeMain()[MdeModulePkg/Core/D
13 matches
Mail list logo
