Date   

Re: Whitley Coyote Pass support

Nate DeSimone
 

Hi Damien,

For Ice Lake specifically, there are MinPlatform 2 board ports that have been discussed publicly. The first one is for Junction City, which is a OCP platform jointly developed by Intel and Wiwynn. http://files.opencompute.org/oc/public.php?service=files&t=fcb376efa953f3f797c97bf1a9ac8365&download

The second is Super Micro plans to demonstrate MinPlatform running on one of their Ice Lake boards at the OCP summit in November.

I am not aware of any porting work happening for Coyote Pass specifically.

Hope that helps,
Nate

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Oram, Isaac W
Sent: Tuesday, October 12, 2021 4:43 PM
To: discuss@edk2.groups.io; dlagneux@upmem.com
Subject: Re: [edk2-discuss] Whitley Coyote Pass support

Damien,

I am not aware of any plans to provide open ports of the Intel board or system products, which would include Coyote Pass.

I believe that there is production board porting activity in the Open Compute Project (OCP) Open System Firmware (OSF) context. https://www.opencompute.org/projects/open-system-firmware if you are interested. I believe some open system firmware solutions to be discussed and demonstrated at the OCP Global Summit later this year.

Regards,
Isaac

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Damien Lagneux
Sent: Wednesday, October 6, 2021 8:36 AM
To: discuss@edk2.groups.io
Subject: [edk2-discuss] Whitley Coyote Pass support

Hi everyone,

I saw that you are already supporting the Wilson City platform for the Whitley generation.

I would like to know if the support for the Coyote Pass platform is also planned to be released?

BR,
--

*Damien Lagneux*
UPMEM
* System **Tech Lead*


Re: Whitley Coyote Pass support

Oram, Isaac W
 

Damien,

I am not aware of any plans to provide open ports of the Intel board or system products, which would include Coyote Pass.

I believe that there is production board porting activity in the Open Compute Project (OCP) Open System Firmware (OSF) context. https://www.opencompute.org/projects/open-system-firmware if you are interested. I believe some open system firmware solutions to be discussed and demonstrated at the OCP Global Summit later this year.

Regards,
Isaac

-----Original Message-----
From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of Damien Lagneux
Sent: Wednesday, October 6, 2021 8:36 AM
To: discuss@edk2.groups.io
Subject: [edk2-discuss] Whitley Coyote Pass support

Hi everyone,

I saw that you are already supporting the Wilson City platform for the Whitley generation.

I would like to know if the support for the Coyote Pass platform is also planned to be released?

BR,
--

*Damien Lagneux*
UPMEM
* System **Tech Lead*


Whitley Coyote Pass support

Damien Lagneux
 

Hi everyone,

I saw that you are already supporting the Wilson City platform for the
Whitley generation.

I would like to know if the support for the Coyote Pass platform is also
planned to be released?

BR,
--

*Damien Lagneux*
UPMEM
* System **Tech Lead*


Re: Guid.xref file

Konstantin Aladyshev
 

I've registered in the tianocore bugzilla and have filed a bug:
https://bugzilla.tianocore.org/show_bug.cgi?id=3685

On Mon, Oct 11, 2021 at 5:36 AM Andrew (EFI) Fish <afish@apple.com> wrote:



Sent from my iPhone

On Oct 10, 2021, at 9:37 PM, gaoliming <gaoliming@byosoft.com.cn> wrote:

Guid.xref includes all Guid/Ppi/Protocol guid and module FILE_GUID in one platform DSC/FDF.

If Guid is generated into AutoGen, it should be included in Guid.xref.
That does not seem to be happening. We should file a BZ if one does not get filed.

Thanks,

Andrew Fish

Thanks
Liming
-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Andrew
Fish via groups.io
发送时间: 2021年10月10日 23:28
收件人: discuss <discuss@edk2.groups.io>; aladyshev22@gmail.com
主题: Re: [edk2-discuss] Guid.xref file



On Oct 10, 2021, at 3:33 AM, Konstantin Aladyshev
<aladyshev22@gmail.com> wrote:

Hello!

Sometimes it's useful to transform GUID values to their names from the
codebase. For example when you investigate the boot log.
Usually I just use key/value pairs from the generated build file
`Build/OvmfX64/DEBUG_GCC5/FV/Guid.xref, and perform necessary
substitutions in the log file through the simple custom python script.
This Guid.xref file has associations like this:
```
6302D008-7F9B-4F30-87AC-60C9FEF5DA4E gEfiShellProtocolGuid
```
So it is easy to construct a dictionary with GUID/Name pairs with it.
But the problem is that this file doesn't contain all the GUID/Name pairs.
For example
gShellNetwork1HiiGuid/gShellLevel2HiiGuid/gEfiComponentNameProtocolGui
d
are not present in this file.
Which GUIDs go to the `Build/OvmfX64/RELEASE_GCC5/FV/Guid.xref` file
and which don't?
It looks like the HII related GUDs [1] don’t end up in the Guid.xref file. That
seems like a bug, please file a BZ. I would expect every GUID in all the
modules AutoGen.c file to show up in the Guid.xref file.

[1] example
/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gEfiAcpiTableProtocolGuid -- '*.xref' '*.c'
DEBUG_XCODE5/FV/Guid.xref:309:FFE06BDD-6107-46A6-7BB2-5A9C7EC527
5C gEfiAcpiTableProtocolGuid
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/AcpiTableDxe/AcpiTabl
eDxe/DEBUG/AutoGen.c:34:GLOBAL_REMOVE_IF_UNREFERENCED
EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B,
0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/BootGraphicsResource
TableDxe/BootGraphicsResourceTableDxe/DEBUG/AutoGen.c:31:GLOBAL_RE
MOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Disk/RamDiskDxe/RamDisk
Dxe/DEBUG/AutoGen.c:43:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/NetworkPkg/IScsiDxe/IScsiDxe/DEBUG/AutoGen.c:41:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpiPlatformDx
e/DEBUG/AutoGen.c:27:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:13
9:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellLevel2HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:64:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellLevel2HiiGuid =
{0xf95a7ccc, 0x4c55, 0x4426, {0xa7, 0xb4, 0xdc, 0x89, 0x61, 0x95, 0xb,
0xae}};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellNetwork1HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:71:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellNetwork1HiiGuid =
{0xf3d301bb, 0xf4a5, 0x45a8, {0xb0, 0xb7, 0xfa, 0x99, 0x9c, 0x62, 0x37,
0xae}};

Thanks,

Andrew Fish

Best regards,
Konstantin Aladyshev









Re: Guid.xref file

Andrew Fish
 

On Oct 10, 2021, at 9:37 PM, gaoliming <gaoliming@byosoft.com.cn> wrote:

Guid.xref includes all Guid/Ppi/Protocol guid and module FILE_GUID in one platform DSC/FDF.

If Guid is generated into AutoGen, it should be included in Guid.xref.
That does not seem to be happening. We should file a BZ if one does not get filed.

Thanks,

Andrew Fish

Thanks
Liming
-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Andrew
Fish via groups.io
发送时间: 2021年10月10日 23:28
收件人: discuss <discuss@edk2.groups.io>; aladyshev22@gmail.com
主题: Re: [edk2-discuss] Guid.xref file



On Oct 10, 2021, at 3:33 AM, Konstantin Aladyshev
<aladyshev22@gmail.com> wrote:

Hello!

Sometimes it's useful to transform GUID values to their names from the
codebase. For example when you investigate the boot log.
Usually I just use key/value pairs from the generated build file
`Build/OvmfX64/DEBUG_GCC5/FV/Guid.xref, and perform necessary
substitutions in the log file through the simple custom python script.
This Guid.xref file has associations like this:
```
6302D008-7F9B-4F30-87AC-60C9FEF5DA4E gEfiShellProtocolGuid
```
So it is easy to construct a dictionary with GUID/Name pairs with it.
But the problem is that this file doesn't contain all the GUID/Name pairs.
For example
gShellNetwork1HiiGuid/gShellLevel2HiiGuid/gEfiComponentNameProtocolGui
d
are not present in this file.
Which GUIDs go to the `Build/OvmfX64/RELEASE_GCC5/FV/Guid.xref` file
and which don't?
It looks like the HII related GUDs [1] don’t end up in the Guid.xref file. That
seems like a bug, please file a BZ. I would expect every GUID in all the
modules AutoGen.c file to show up in the Guid.xref file.

[1] example
/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gEfiAcpiTableProtocolGuid -- '*.xref' '*.c'
DEBUG_XCODE5/FV/Guid.xref:309:FFE06BDD-6107-46A6-7BB2-5A9C7EC527
5C gEfiAcpiTableProtocolGuid
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/AcpiTableDxe/AcpiTabl
eDxe/DEBUG/AutoGen.c:34:GLOBAL_REMOVE_IF_UNREFERENCED
EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B,
0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/BootGraphicsResource
TableDxe/BootGraphicsResourceTableDxe/DEBUG/AutoGen.c:31:GLOBAL_RE
MOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Disk/RamDiskDxe/RamDisk
Dxe/DEBUG/AutoGen.c:43:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/NetworkPkg/IScsiDxe/IScsiDxe/DEBUG/AutoGen.c:41:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpiPlatformDx
e/DEBUG/AutoGen.c:27:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:13
9:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellLevel2HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:64:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellLevel2HiiGuid =
{0xf95a7ccc, 0x4c55, 0x4426, {0xa7, 0xb4, 0xdc, 0x89, 0x61, 0x95, 0xb,
0xae}};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellNetwork1HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:71:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellNetwork1HiiGuid =
{0xf3d301bb, 0xf4a5, 0x45a8, {0xb0, 0xb7, 0xfa, 0x99, 0x9c, 0x62, 0x37,
0xae}};

Thanks,

Andrew Fish

Best regards,
Konstantin Aladyshev









Re: How to generate .gcda files

Andrew Fish
 

I don’t know of any support so you must have updated the compiler flags?

On Oct 10, 2021, at 9:29 PM, wenyi,xie via groups.io <xiewenyi2=huawei.com@groups.io> wrote:

Hello, everyone

Does any one know how to generate .gcda file in EDK2 for unit test. I want to get .gcda files from EDK2 so that I can use lcov to calculate the unit test coverage.
I searched .gcda files in Build folder in my old EDK2 repository(this repository run build and CI locally before) and found .gcda files, but I am not sure when and how were they generated. When I download a new edk2 repository and locally run CI command "stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=GCC5", there were no .gcda files generated.

Thanks
Wenyi





回复: [edk2-discuss] Guid.xref file

gaoliming
 

Guid.xref includes all Guid/Ppi/Protocol guid and module FILE_GUID in one platform DSC/FDF.

If Guid is generated into AutoGen, it should be included in Guid.xref.

Thanks
Liming

-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Andrew
Fish via groups.io
发送时间: 2021年10月10日 23:28
收件人: discuss <discuss@edk2.groups.io>; aladyshev22@gmail.com
主题: Re: [edk2-discuss] Guid.xref file



On Oct 10, 2021, at 3:33 AM, Konstantin Aladyshev
<aladyshev22@gmail.com> wrote:

Hello!

Sometimes it's useful to transform GUID values to their names from the
codebase. For example when you investigate the boot log.
Usually I just use key/value pairs from the generated build file
`Build/OvmfX64/DEBUG_GCC5/FV/Guid.xref, and perform necessary
substitutions in the log file through the simple custom python script.
This Guid.xref file has associations like this:
```
6302D008-7F9B-4F30-87AC-60C9FEF5DA4E gEfiShellProtocolGuid
```
So it is easy to construct a dictionary with GUID/Name pairs with it.
But the problem is that this file doesn't contain all the GUID/Name pairs.
For example
gShellNetwork1HiiGuid/gShellLevel2HiiGuid/gEfiComponentNameProtocolGui
d
are not present in this file.
Which GUIDs go to the `Build/OvmfX64/RELEASE_GCC5/FV/Guid.xref` file
and which don't?
It looks like the HII related GUDs [1] don’t end up in the Guid.xref file. That
seems like a bug, please file a BZ. I would expect every GUID in all the
modules AutoGen.c file to show up in the Guid.xref file.

[1] example
/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gEfiAcpiTableProtocolGuid -- '*.xref' '*.c'
DEBUG_XCODE5/FV/Guid.xref:309:FFE06BDD-6107-46A6-7BB2-5A9C7EC527
5C gEfiAcpiTableProtocolGuid
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/AcpiTableDxe/AcpiTabl
eDxe/DEBUG/AutoGen.c:34:GLOBAL_REMOVE_IF_UNREFERENCED
EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B,
0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/BootGraphicsResource
TableDxe/BootGraphicsResourceTableDxe/DEBUG/AutoGen.c:31:GLOBAL_RE
MOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Disk/RamDiskDxe/RamDisk
Dxe/DEBUG/AutoGen.c:43:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/NetworkPkg/IScsiDxe/IScsiDxe/DEBUG/AutoGen.c:41:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid =
{ 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27,
0x5C }};
DEBUG_XCODE5/X64/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpiPlatformDx
e/DEBUG/AutoGen.c:27:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:13
9:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID
gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2,
0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellLevel2HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:64:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellLevel2HiiGuid =
{0xf95a7ccc, 0x4c55, 0x4426, {0xa7, 0xb4, 0xdc, 0x89, 0x61, 0x95, 0xb,
0xae}};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked
--no-exclude-standard gShellNetwork1HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:71:
GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellNetwork1HiiGuid =
{0xf3d301bb, 0xf4a5, 0x45a8, {0xb0, 0xb7, 0xfa, 0x99, 0x9c, 0x62, 0x37,
0xae}};

Thanks,

Andrew Fish

Best regards,
Konstantin Aladyshev








How to generate .gcda files

wenyi,xie
 

Hello, everyone

Does any one know how to generate .gcda file in EDK2 for unit test. I want to get .gcda files from EDK2 so that I can use lcov to calculate the unit test coverage.
I searched .gcda files in Build folder in my old EDK2 repository(this repository run build and CI locally before) and found .gcda files, but I am not sure when and how were they generated. When I download a new edk2 repository and locally run CI command "stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=GCC5", there were no .gcda files generated.

Thanks
Wenyi


Re: Guid.xref file

Andrew Fish
 

On Oct 10, 2021, at 3:33 AM, Konstantin Aladyshev <aladyshev22@gmail.com> wrote:

Hello!

Sometimes it's useful to transform GUID values to their names from the
codebase. For example when you investigate the boot log.
Usually I just use key/value pairs from the generated build file
`Build/OvmfX64/DEBUG_GCC5/FV/Guid.xref, and perform necessary
substitutions in the log file through the simple custom python script.
This Guid.xref file has associations like this:
```
6302D008-7F9B-4F30-87AC-60C9FEF5DA4E gEfiShellProtocolGuid
```
So it is easy to construct a dictionary with GUID/Name pairs with it.
But the problem is that this file doesn't contain all the GUID/Name pairs.
For example gShellNetwork1HiiGuid/gShellLevel2HiiGuid/gEfiComponentNameProtocolGuid
are not present in this file.
Which GUIDs go to the `Build/OvmfX64/RELEASE_GCC5/FV/Guid.xref` file
and which don't?
It looks like the HII related GUDs [1] don’t end up in the Guid.xref file. That seems like a bug, please file a BZ. I would expect every GUID in all the modules AutoGen.c file to show up in the Guid.xref file.

[1] example
/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked --no-exclude-standard gEfiAcpiTableProtocolGuid -- '*.xref' '*.c'
DEBUG_XCODE5/FV/Guid.xref:309:FFE06BDD-6107-46A6-7BB2-5A9C7EC5275C gEfiAcpiTableProtocolGuid
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/AcpiTableDxe/AcpiTableDxe/DEBUG/AutoGen.c:34:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Acpi/BootGraphicsResourceTableDxe/BootGraphicsResourceTableDxe/DEBUG/AutoGen.c:31:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskDxe/DEBUG/AutoGen.c:43:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/NetworkPkg/IScsiDxe/IScsiDxe/DEBUG/AutoGen.c:41:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpiPlatformDxe/DEBUG/AutoGen.c:27:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:139:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gEfiAcpiTableProtocolGuid = { 0xFFE06BDD, 0x6107, 0x46A6, { 0x7B, 0xB2, 0x5A, 0x9C, 0x7E, 0xC5, 0x27, 0x5C }};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked --no-exclude-standard gShellLevel2HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:64:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellLevel2HiiGuid = {0xf95a7ccc, 0x4c55, 0x4426, {0xa7, 0xb4, 0xdc, 0x89, 0x61, 0x95, 0xb, 0xae}};

/Volumes/Case/edk2-github/Build/OvmfX64(master)>git grep --untracked --no-exclude-standard gShellNetwork1HiiGuid -- '*.xref' '*.c'
DEBUG_XCODE5/X64/ShellPkg/Application/Shell/Shell/DEBUG/AutoGen.c:71:GLOBAL_REMOVE_IF_UNREFERENCED EFI_GUID gShellNetwork1HiiGuid = {0xf3d301bb, 0xf4a5, 0x45a8, {0xb0, 0xb7, 0xfa, 0x99, 0x9c, 0x62, 0x37, 0xae}};

Thanks,

Andrew Fish

Best regards,
Konstantin Aladyshev





Re: Different methods for declaring UNI files

Andrew Fish
 

On Oct 10, 2021, at 5:12 AM, Konstantin Aladyshev <aladyshev22@gmail.com> wrote:

Hello!

I was investigating EDKII database and have found 3 ways of declaring UNI files:

1) Sources section within the INF file:
```
[Sources]
InventoryStrings.uni
VfrStrings.uni
...
```

Example:
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal/DriverSampleDxe/DriverSampleDxe.inf


2) MODULE_UNI_FILE/[UserExtensions.TianoCore."ExtraFiles"] within the INF file:
```
[Defines]
...
MODULE_UNI_FILE = ResetSystemPei.uni

...

[UserExtensions.TianoCore."ExtraFiles"]
ResetSystemPeiExtra.uni
```
Example: https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal/ResetSystemPei/ResetSystemPei.inf

3) PACKAGE_UNI_FILE/[UserExtensions.TianoCore."ExtraFiles"] within the DEC file:
```
[Defines]
PACKAGE_UNI_FILE = MdeModulePkg.uni

...

[UserExtensions.TianoCore."ExtraFiles"]
MdeModulePkgExtra.uni
```
Example: https://github.com/tianocore/edk2/blob/master/MdeModulePkg/MdeModulePkg.dec

_______________________

Could someone provide me some info about all these different methods?

As I understand, all the translation strings for HII should be defined
within method 1. Am I correct?
What is the purpose of methods 2 and 3 then?
Konstantin,

Your 2) and 3) are associated with the UEFI Packaging Specification [1]. You can read up on what things in the INF file mean here [2]. I think 2.16.1 will answer your questions.

TL;DR these files are not processed by the build system and used for other things.

[1] https://uefi.org/sites/default/files/resources/Dist_Package_Spec_1_1.pdf

[2] https://tianocore-docs.github.io/edk2-InfSpecification/release-1.27/2_inf_overview/216_[userextensions]_section.html#216-userextensions-section

Thanks,

Andrew Fish

I see that these methods define strings like:
STR_MODULE_ABSTRACT
STR_MODULE_DESCRIPTION
STR_PROPERTIES_MODULE_NAME

STR_PACKAGE_ABSTRACT
STR_PACKAGE_DESCRIPTION
STR_PROPERTIES_PACKAGE_NAME

When are these strings printed? What is the point of putting
STR_MODULE_ABSTRACT/STR_MODULE_DESCRIPTION in one file and
STR_PROPERTIES_MODULE_NAME in the other "extra" file? Seems redundant.

Also I've found more strange strings in the
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/MdeModulePkg.uni

STR_gEfiMdeModulePkgTokenSpaceGuid_PcdLoadModuleAtFixAddressEnable_PROMPT
STR_gEfiMdeModulePkgTokenSpaceGuid_PcdLoadModuleAtFixAddressEnable_HELP
STR_gEfiMdeModulePkgTokenSpaceGuid_ERR_80000001

How are they used?

Best regards,
Konstantin Aladyshev





Different methods for declaring UNI files

Konstantin Aladyshev
 

Hello!

I was investigating EDKII database and have found 3 ways of declaring UNI files:

1) Sources section within the INF file:
```
[Sources]
InventoryStrings.uni
VfrStrings.uni
...
```

Example:
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal/DriverSampleDxe/DriverSampleDxe.inf


2) MODULE_UNI_FILE/[UserExtensions.TianoCore."ExtraFiles"] within the INF file:
```
[Defines]
...
MODULE_UNI_FILE = ResetSystemPei.uni

...

[UserExtensions.TianoCore."ExtraFiles"]
ResetSystemPeiExtra.uni
```
Example: https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Universal/ResetSystemPei/ResetSystemPei.inf

3) PACKAGE_UNI_FILE/[UserExtensions.TianoCore."ExtraFiles"] within the DEC file:
```
[Defines]
PACKAGE_UNI_FILE = MdeModulePkg.uni

...

[UserExtensions.TianoCore."ExtraFiles"]
MdeModulePkgExtra.uni
```
Example: https://github.com/tianocore/edk2/blob/master/MdeModulePkg/MdeModulePkg.dec

_______________________

Could someone provide me some info about all these different methods?

As I understand, all the translation strings for HII should be defined
within method 1. Am I correct?
What is the purpose of methods 2 and 3 then?
I see that these methods define strings like:
STR_MODULE_ABSTRACT
STR_MODULE_DESCRIPTION
STR_PROPERTIES_MODULE_NAME

STR_PACKAGE_ABSTRACT
STR_PACKAGE_DESCRIPTION
STR_PROPERTIES_PACKAGE_NAME

When are these strings printed? What is the point of putting
STR_MODULE_ABSTRACT/STR_MODULE_DESCRIPTION in one file and
STR_PROPERTIES_MODULE_NAME in the other "extra" file? Seems redundant.

Also I've found more strange strings in the
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/MdeModulePkg.uni

STR_gEfiMdeModulePkgTokenSpaceGuid_PcdLoadModuleAtFixAddressEnable_PROMPT
STR_gEfiMdeModulePkgTokenSpaceGuid_PcdLoadModuleAtFixAddressEnable_HELP
STR_gEfiMdeModulePkgTokenSpaceGuid_ERR_80000001

How are they used?

Best regards,
Konstantin Aladyshev


Guid.xref file

Konstantin Aladyshev
 

Hello!

Sometimes it's useful to transform GUID values to their names from the
codebase. For example when you investigate the boot log.
Usually I just use key/value pairs from the generated build file
`Build/OvmfX64/DEBUG_GCC5/FV/Guid.xref, and perform necessary
substitutions in the log file through the simple custom python script.
This Guid.xref file has associations like this:
```
6302D008-7F9B-4F30-87AC-60C9FEF5DA4E gEfiShellProtocolGuid
```
So it is easy to construct a dictionary with GUID/Name pairs with it.
But the problem is that this file doesn't contain all the GUID/Name pairs.
For example gShellNetwork1HiiGuid/gShellLevel2HiiGuid/gEfiComponentNameProtocolGuid
are not present in this file.
Which GUIDs go to the `Build/OvmfX64/RELEASE_GCC5/FV/Guid.xref` file
and which don't?

Best regards,
Konstantin Aladyshev


Re: Coreboot+UEFI to boot Linux -memory issue

Ghorai, Sukumar
 

Hi,
I am able to boot Linux using (coreboot+ TianoCore).
however Kernel always see the total available memory as 2GB only.

I feel coreboot pass the memory information to UEFI payload, which forwarded to Kernel init.

1. is that any acpi table missing in coreboot?
2. and how memory information passed from coreboot to UEFI payload.

pls let me know what are the steps to debug this issue!!

Thx & rgds,
Sukumar


Some codes in EDKII do not obey the EDK II C Coding Standards Specification

than1@...
 

Hello there,

I am new to EDKII and reading some standards published by the EDKII project. There is a item that says,

5.6.1.2 The use of int, unsigned, char, void, static, long is a violation of the coding convention,

But I found some place in current newest master branch that use static keywords to define EFI functions like

CryptoPkg\Library\BaseCryptLibOnProtocolPpi\CryptLib.c, line 88
CryptoPkg\Driver\Crypto.c, line 79,97

Also, some codes in BaseTools and git submodules use the static keyword, which I think they are out of question,
since they are not EDKII packages.

Do anyone share the similar opinion with me, or do someone know whether the maintainer has the plan to fix these code?

Thanks,
Toyoharu


Re: Make HII browser engine render faster and change font Size in HII

Kiet Pham
 

Dear Liming

What a pitty that edk2 cannot change font size natively. Thanks for your
response, anyway

Kiet

-----Original Message-----
From: gaoliming [mailto:gaoliming@byosoft.com.cn]
Sent: Wednesday, September 29, 2021 9:36 AM
To: discuss@edk2.groups.io; kiet.pham@xelex.vn
Cc: 'shenjiabin' <shenjiabin@byosoft.com.cn>
Subject: 回复: [edk2-discuss] Make HII browser engine render faster and
change font Size in HII

Kiet:
Each font is specified as EFI_NARROW_GLYPH that has a preferred dimension
(w x h) of 8 x 19 pixels.

So, font size is not changed.

Thanks
Liming
-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Kiet Pham
发送时间: 2021年9月24日 18:19
收件人: discuss@edk2.groups.io
主题: [edk2-discuss] Make HII browser engine render faster and change
font Size in HII

Hello All,



I'm currently develop BIOS Setup Utilities. The monitor resolution is
too big 1920 x 1080 so when I try to set BIOS setup full screen, it
took short but noticeable render time to render the BIOS Setup. Also,
I cannot find
any
way to modify font size, most are just changing character "container"
size without changing character size.



So I'd like to ask how to make HII Browser Engine render faster and
technique to adjust font size.



Thanks in advance,

Kiet







回复: [edk2-discuss] Make HII browser engine render faster and change font Size in HII

gaoliming
 

Kiet:
Each font is specified as EFI_NARROW_GLYPH that has a preferred dimension
(w x h) of 8 x 19 pixels.

So, font size is not changed.

Thanks
Liming
-----邮件原件-----
发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Kiet Pham
发送时间: 2021年9月24日 18:19
收件人: discuss@edk2.groups.io
主题: [edk2-discuss] Make HII browser engine render faster and change font
Size in HII

Hello All,



I'm currently develop BIOS Setup Utilities. The monitor resolution is too
big 1920 x 1080 so when I try to set BIOS setup full screen, it took short
but noticeable render time to render the BIOS Setup. Also, I cannot find
any
way to modify font size, most are just changing character "container" size
without changing character size.



So I'd like to ask how to make HII Browser Engine render faster and
technique to adjust font size.



Thanks in advance,

Kiet







Re: a question about X509 flag

Marvin Häuser
 

Hey Wenyi,

Sorry, I cannot help with the time one, but "partial chain" is how virtually any other crypto-solution works out-of-the-box. Basically there is a disagreement about what defines a root certificate, and while some think it is the OpenSSL default of requiring a self-signed certificate for root, many people including myself strongly disagree and do not believe it follows from the RFCs. I'm not aware of any bad security implications of either model. So, this merely allows any certificate in the chain (the top one may be self-signed *if* it even is a certificate, it may just as well be a trusted public key for all we know) to be eligible to be added to the trust store and root a trust chain.

Further reading: https://github.com/openssl/openssl/issues/7871

Cc CryptoPkg maintainers and edk2-devel for further feedback

Best regards,
Marvin

On 27/09/2021 10:53, wenyi,xie via groups.io wrote:
Hello,

I have a question about flag set in X509_STORE. Does anyone know why need to set flags X509_V_FLAG_PARTIAL_CHAIN and X509_V_FLAG_NO_CHECK_TIME to X509Store in TlsNew() (CryptoPkg\Library\TlsLib\TlsInit.c)

Thanks
Wenyi




Make HII browser engine render faster and change font Size in HII

Kiet Pham
 

Hello All,



I'm currently develop BIOS Setup Utilities. The monitor resolution is too
big 1920 x 1080 so when I try to set BIOS setup full screen, it took short
but noticeable render time to render the BIOS Setup. Also, I cannot find any
way to modify font size, most are just changing character "container" size
without changing character size.



So I'd like to ask how to make HII Browser Engine render faster and
technique to adjust font size.



Thanks in advance,

Kiet


Is the QemuVideoDXE GOP gone after S3

Joel
 

I was wondering if anyone knew if the Graphical Output Protocol that creates the framebuffer for the guests is no longer instantiated after OVMF comes back from S3 resume. If I uninstall my guest PV driver for display, I no longer get screen updates after the guest has gone to sleep. It will fall back to the GOP framebuffer correctly before S3. Is there a large amount of work that needs to be done to get this type of thing working? I'm unsure if we just need to add the tables to the LockBox for the GOP during EndOfDxe events or something. Any help would be great.

-Joel


Writing to QemuVideoDxe Framebuffer after sleep

Joel
 

I have been working with the Xen platform, and while I have gotten sleep working, I have run into a bug that I need help understanding. We use our own PV drivers for display, and if we disable the driver or uninstall before the guest has gone to sleep, the video will switch over to the GOP QemuVideo (using the Bochs protocol) without issue. However if a sleep has been done and an uninstall performed, I am seeing the last image before the framebuffer switched to the PV buffer (so Windows boot screen), and the framebuffer isn't updated beyond that. From what it appears, it would seem that after the guest has gone to sleep, the framebuffer setup by QemuVideo is destroyed and not set back up on return. From what I have read the GOP gets setup and is just never torn down after the end of DXE. Does anyone have any idea what it would take to get the GOP running after sleep, or does anyone know that it is most definitely running and therefore my problem exists elsewhere?

This is my first post to the group, so any help would be fantastic!

-Joel

41 - 60 of 897