Hi,
In this page http://www.coreboot.org/TianoCore , It is said that TianoCore
could be a payload of coreboot to implement opensource UEFI environment.
Now, I have built UDK(UEFI development Kit) successfully.
Then what to do next? how to use these as payload of coreboot?
--
Yours sincerely,
WANG
hi, Stephen:
PE header has an item to indicate it's 32bit / x64 / ARM .
Every efi driver binary is PE format.
best wishes,
-邮件原件-
发件人: Stephen Polkowski [mailto:step...@centtech.com]
发送时间: 2012年12月4日 0:03
收件人: edk2-devel@lists.sourceforge.net
主题: [edk2] How to determine UEFI arch
Hello Wissam,
There are a few things to check that are not clearly stated in the
PythonReadMe.txt file.
Make sure that you are using the os.py, ntpath.py, pydoc.py, and site.py files
from PyMod-2.7.2/Lib, instead of the versions from Python-2.7.2/Lib.
If you start Python with the -S option, it
Stephen,
Thank you for reporting this.
I have added the issue to the queue of things to work on for StdLib.
The fix will depend upon whether GCC4.6 is actually calling this an error or it
is a warning being promoted to an error. If a promoted warning, the fix will
be to just turn off that speci
UEFI is focused on defining the interfaces to option ROMs and OS loaders, and
pushing policy decisions, where possible, in the platform firmware. UEFI tends
to not define how the construct the platform Firmware. The UEFI PI specs go
into more detail of firmware construction, but mostly so modul
Sounds like a bug to me.
Thanks,
Andrew
On Dec 3, 2012, at 3:00 PM, justin_johns...@dell.com wrote:
> Hi all,
> I have some binary-only drivers with dependency expressions that are not
> being processed. These drivers are not UEFI model drivers.
>
> I see in WorkspaceDatabase.py:
> # If the
Hi all,
I have some binary-only drivers with dependency expressions that are not being
processed. These drivers are not UEFI model drivers.
I see in WorkspaceDatabase.py:
# If the module has only Binaries and no Sources, then ignore [Depex]
if self.Sources == None or self.Sources == []:
if se
Hi there,
I am wondering if there are any calls in edk2 or the UEFI spec to locate
the system's BIOS code and dump it to disk or some other medium. I want to
implement this in a UEFI driver. I have seen plenty of information
regarding option ROMs in the spec and driver guide but not on the BIOS
co
Thanks!
From: Carsey, Jaben [mailto:jaben.car...@intel.com]
Sent: Monday, December 03, 2012 10:41 AM
To: Phillips, Chris J (BCS CFE)
Cc: edk2-devel@lists.sourceforge.net; Carsey, Jaben
Subject: RE: [CodeReview] ShellPkg remove "2.0" prefix text from shell prompt
Complete.
13982.
From: Phillips,
FYI, I checked the alignment of the DTB in the failing case (ie: your kernel
and your dtb) and the DTB is loaded at 0x80002000 (DRAM starts at
0x8000).
-Original Message-
From: Olivier Martin [mailto:olivier.mar...@arm.com]
Sent: 03 December 2012 19:09
To: Nicola Johnsen; edk2-devel@l
I tried with the binary kernel and device tree you sent me a while ago.
After changing the DSC file to enable booting Linux with a Device Tree:
--- a/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-A15_MPCore.dsc
+++ b/ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-A15_MPCore.dsc
@@ -147,7 +147,8 @
Hello,
I'm trying to build the AppPkg on Ubuntu 12.04 using the
native installed complier. GCC4.6 fails with the following message:
/UDK2010.SR1/StdLib/LibC/Uefi/SysCalls.c: In function ‘utimes’:
/UDK2010.SR1/StdLib/LibC/Uefi/SysCalls.c:1250:11: error: ‘va_start’ used
in function with f
Complete.
13982.
From: Phillips, Chris J (BCS CFE) [mailto:chr...@hp.com]
Sent: Friday, November 30, 2012 2:52 PM
To: Carsey, Jaben
Cc: edk2-devel@lists.sourceforge.net
Subject: [CodeReview] ShellPkg remove "2.0" prefix text from shell prompt
Importance: High
Please review the attached .uni file
Hi,
I've been looking for a way to determine the host
architecture from a shell script. Basically, I want to know
if the system is 32 bits or 64 bits. I don't see any UEFI variables
that would allow a shell script to know the architecture size.
Am I missing something?
Thanks,
Hello Prasad,
Which revision of the BeagleBoard are you using? And which type and size of
MMC/SD/MMCplus/SDHC card are you using ?
What might happen is UEFI fails to reset the MMC controller to start again
the MMC state machine from the MMC Identification mode after u-boot did it.
There are two s
Thanks Andrew for your reply.
Regards,
Ramesh
From: Andrew Fish [af...@apple.com]
Sent: Monday, December 03, 2012 12:47 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Protocol Uninstall
On Dec 2, 2012, at 10:21 PM, Ramesh Raju wrote:
Andrew,
16 matches
Mail list logo