Hi, Laszlo
I have updated the copyright and comments in EDKII 14355.
Best Regards,
Fu, Siyuan
-Original Message-
From: Laszlo Ersek [mailto:ler...@redhat.com]
Sent: Friday, May 10, 2013 6:15 PM
To: Fu, Siyuan
Cc: edk2-devel@lists.sourceforge.net; Fan, Jeff
Subject: Re: [edk2] [PATCH] M
Chip,
The specs I know about are located here:
http://www.intel.com/content/www/us/en/architecture-and-technology/unified-extensible-firmware-interface/efi-specifications-general-technology.html
I don't see the Framework MP Services Protocol in this set, can't remember if
it is hiding in one
Daryl,
I can't find a specification for the Framework MP Services Protocol.
Do you know of one?
-chip
On Mon, May 13, 2013 at 2:16 PM, Mcdaniel, Daryl
wrote:
> Dan,
>
> Are you using the Framework MP Services protocol or the PI MP Services
> protocol?
> You can use both protocols in a non-bloc
On Mon, May 13, 2013 at 1:32 PM, Olivier Martin wrote:
> And also
This patch was Reviewed-by you?
> apply the related changes of the attached patch.
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Olivier Martin
Can you post this as a separate patch with a commit mes
Yes
From: Mcdaniel, Daryl [mailto:daryl.mcdan...@intel.com]
Sent: Monday, May 13, 2013 2:35 PM
To: edk2-devel@lists.sourceforge.net
Cc: Tim Lewis
Subject: RE: [edk2] x86 compiler intrinsics
Tim,
If the compiler "instinsic" libraries (both gcc and msvc) from StdLib were made
available separately
Tim,
If the compiler "instinsic" libraries (both gcc and msvc) from StdLib were made
available separately and for general use (though still as part of EDK II),
would this satisfy your needs? This would get you memcpy/memmove as well as
the intrinsics needed to use the C math operators, +-*/%^
Dan,
Are you using the Framework MP Services protocol or the PI MP Services protocol?
You can use both protocols in a non-blocking manner, but there are some
differences.
First, define an event to be passed to the StartupThisAP() or StartupAllAPs()
functions.
Framework MP Services Protocol:
And also apply the related changes of the attached patch.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
Thanks,
Olivier
> -Original Message-
> From: Jordan Justen [mailto:jordan.l.jus...@intel.com]
> Sent: 10 May 2013 04:08
> To: edk2-devel@lists
Tested with the e1000, ne2k_pci, pcnet, rtl8139, and virtio iPXE UEFI
oprom drivers distributed with qemu-1.5.0-rc1. Also tested with Intel's
e1000 driver.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
OvmfPkg/Library/PlatformBdsLib/QemuBootOrder.c |
DHCP, PXE, and StdLib socket apps are enabled in OVMF by the sum of:
(a) a UEFI NIC driver,
(b) the generic network stack.
The only choice for (a) used to be the proprietary Intel E1000 driver,
which is cumbersome to obtain and enable.
The iPXE UEFI NIC drivers packaged with qemu-1.5 cover (a) fo
With the iPXE EFI oproms we can PXE boot in OVMF on all qemu NICs.
Laszlo Ersek (2):
OvmfPkg: enable the generic network stack by default
OvmfPkg: QemuBootOrder: recognize Ethernet OFW device paths
OvmfPkg/Library/PlatformBdsLib/QemuBootOrder.c | 29
OvmfPkg/OvmfPkgIa32.dsc
We found an issue where the current implementation of PiSmmIpl
(MdeModulePkg/Core/PiSmmCore) does not appear to follow the PI specification.
The PI specification, volume 4, section 1.4, step 4, states: "The SMM IPL DXE
driver (dependent on the EFI_SMM_ACCESS2_PROTOCOL,
EFI_SMM_CONTROL2_PROTOCOL
On May 13, 2013, at 2:02 AM, Jeffrey Chou wrote:
> Hi Daryl,
>
> Thanks for your advice. Currently I just have the workaround that my UEFI
> driver invoking a application by LoadImage or ShellExecute, of cause the
> application should be built with StdLib.
> But I encountered some problems w
On 05/07/13 10:50, Laszlo Ersek wrote:
> Tested with the Intel e1000 driver and VirtioNetDxe.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
>
> Signed-off-by: Laszlo Ersek
> ---
> OvmfPkg/Library/PlatformBdsLib/QemuBootOrder.c | 29
>
> 1 files changed,
On 05/03/13 08:09, Laszlo Ersek wrote:
> The tech notes (in the first patch) should say it all.
>
> The series adds files to the tree but doesn't include them in the build
> until the last patch. The series is laid out in logical layers,
> following the structure of the technical notes. Gradual co
On May 13, 2013, at 4:41 AM, "s.v.krishna reddy" wrote:
> Hi,
>
> I have a requirement to build UEFI Drivers with few of pre-built static
> Libraries in Multi platform environment build infrastructure.
>
> Is there any provision for above requirement in EDK2? If so, how do I add
> those pre-
On May 13, 2013, at 1:53 AM, satish kondapalli wrote:
> Thanks Andrew,
>
> I did a simple experiment on Dellr720 server for allocating PCIe DMA capable
> memory. This server has 64GB of physical memory.
>
> First experiment:
> --
>
> In option ROM driver start fun
Hi,
I have a requirement to build UEFI Drivers with few of pre-built static
Libraries in Multi platform environment build infrastructure.
Is there any provision for above requirement in EDK2? If so, how do I add
those pre-built libraries in driver makefile?
Thanks,
Krishna,
-
Hi Daryl,
Thanks for your advice. Currently I just have the workaround that my UEFI
driver invoking a application by LoadImage or ShellExecute, of cause the
application should be built with StdLib.
But I encountered some problems when using LoadImage and ShellExecute:
Case 1:
For ShellExecute, I
Thanks Andrew,
I did a simple experiment on Dellr720 server for allocating PCIe DMA
capable memory. This server has 64GB of physical memory.
First experiment:
--
In option ROM driver start function, i tried allocating different sizes
of memory allocation ( from 128MB to
Hi,
> That should be the case, following Gerd's upstream qemu commit
> c45e5b5b30ac1f5505725a7b36e68cedfce4f01f (from Feb 2013). Starting with
> qemu-1.5.0, these should work out of the box, I believe.
Unless you switch qemu into backward compatibility mode using
'qemu -M pc-${oldversion}'.
>
21 matches
Mail list logo
