Dear MdeModulePkg maintainer,
please find the attached patch that fixes some build issues (ARM toolchain).
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
Regards,
Olivier
-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidentia
Hi Gabrie,
Why do you use legacy method to find SMBIOS entry(like "_SM_")
only in GetQemuSmbiosTables()?
there is no "_SM_" support on ARM platform, but SMBIOS_TABLE_GUID
is usable, could you consider to add SMBIOS_TABLE_GUID
support in that function?
thanks!
Yi
On W
Reviewed-by: Erik Bjorge
From: Carsey, Jaben
Sent: Tuesday, May 13, 2014 3:48 PM
To: Bjorge, Erik C; Shah, Tapan (tapands...@hp.com)
Cc: El-Haj-Mahmoud, Samer (samer.el-haj-mahm...@hp.com); Lohr, Paul A;
edk2-devel@lists.sourceforge.net; Carsey, Jaben
Subject: ShellPkg: Add error messages to CP
The SMBIOS specification requires some structure types to
contain reference fields to other structures' handles. When
InstallAllStructures() rebuilds the SMBIOS tables by traversing
an existing source table, the use of SMBIOS_HANDLE_PI_RESERVED
causes automatically generated, arbitrary handle numbe
Locate QEMU SMBIOS data in fw_cfg and install it via the
SMBIOS protocol.
Starting with qemu-2.1, on pc/x86 machines of type >= 2.1, full
SMBIOS tables are generated and inserted into fw_cfg (i.e., no
per-field patching of locally generated structures is required).
Aside from new code to extract
Hi,
This patch set adds QEMU (2.1 and later) SMBIOS support to OvmfPkg.
Starting with QEMU 2.1, full SMBIOS tables are created and inserted
into fw_cfg. This allows OvmfPkg to reuse most of the pre-existing
Xen code to generate a final SMBIOS table, without the need to apply
fw_cfg per-filed "pat
Hi guys,
I'm working with the mkramdisk.efi application of Efi Toolkit 2.0. However
I can't see a way to free
the resources used by the ram disk after I don't need it anymore. I took a
look into the source code
and I saw that the mkramdisk.efi loads the ramdisk.efi driver to create a
blockIo proto
Reviewed-by: Erik Bjorge
From: Carsey, Jaben
Sent: Tuesday, May 13, 2014 9:22 AM
To: Bjorge, Erik C; Shah, Tapan (tapands...@hp.com)
Cc: edk2-devel@lists.sourceforge.net; Lohr, Paul A; El-Haj-Mahmoud, Samer
(samer.el-haj-mahm...@hp.com); Carsey, Jaben
Subject: ShellPkg: report error when EfiDeco
On 05/13/14 16:55, Ludovic Rousseau wrote:
> 2014-05-13 16:24 GMT+02:00 Laszlo Ersek :
>> Please rebuild your gnu-efi installation with the attached patch, and
>> retest your app.
>
> I still get a crash but with a different message in serial.log
> FS0:\> debug1
> a
> b
> X64 Exception Type
2014-05-13 16:24 GMT+02:00 Laszlo Ersek :
> On 05/13/14 15:50, Ludovic Rousseau wrote:
>> Hello,
>>
>> I hope this is the correct mailing list for my request. If not sorry.
>>
>> I use OVMF-X64-r15214 with qemu version 1.1.2 (Debian
>> 1.1.2+dfsg-6a+deb7u2). It works great for my first tests.
>>
>>
On 05/13/14 15:50, Ludovic Rousseau wrote:
> Hello,
>
> I hope this is the correct mailing list for my request. If not sorry.
>
> I use OVMF-X64-r15214 with qemu version 1.1.2 (Debian
> 1.1.2+dfsg-6a+deb7u2). It works great for my first tests.
>
> I now want to use the DEBUG() call to have some
On Tue, 2014-05-13 at 13:13 +0100, David Woodhouse wrote:
>
> Hi Elvin,
>
> These fields are defined in the v0.98 update to the CSM specification,
> available at
> http://www.intel.com/content/www/us/en/architecture-and-technology/unified-extensible-firmware-interface/efi-compatibility-support-mo
Hello,
I hope this is the correct mailing list for my request. If not sorry.
I use OVMF-X64-r15214 with qemu version 1.1.2 (Debian
1.1.2+dfsg-6a+deb7u2). It works great for my first tests.
I now want to use the DEBUG() call to have some debug traces.
My program is very simple. I use gnu-efi to b
On 05/13/14 14:22, David Woodhouse wrote:
> On Mon, 2014-05-12 at 18:42 +0200, Laszlo Ersek wrote:
>> On 05/12/14 16:00, David Woodhouse wrote:
>>> The addition of UmaAddress/UmaSize fields allows the CSM to have
>>> writable memory between the top of the option ROMs and the start of
>>> its read-o
Hi Michal.
There is a protocol named EFI_SMBIOS_PROTOCOL_GUID defined by the PI Spec.
You can take a llok at this protocol.
Or you can take a llok at this application code (SMBiosView) and check how
it's done there. I believe that SMBiosView does not use this protocol.
Thanks and Regards.
Rafael
On Mon, 2014-05-12 at 18:42 +0200, Laszlo Ersek wrote:
> On 05/12/14 16:00, David Woodhouse wrote:
> > The addition of UmaAddress/UmaSize fields allows the CSM to have
> > writable memory between the top of the option ROMs and the start of
> > its read-only code segment.
> >
> > The HiPermanentMem
On Tue, 2014-05-13 at 03:12 +, Li, Elvin wrote:
> David,
> Where do we initialize
> UmaAddress/UmaSize/HiPermanentMemoryAddress/HiPermanentMemorySize?
> And could you explain the purpose of these new fields?
>
> Thanks
> Elvin
Hi Elvin,
These fields are defined in the v0.98 u
17 matches
Mail list logo
