|
[PATCH 1/1] CryptoPkg: Fix pem heap-buffer-overflow due to BIO_snprintf()
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4075
Fake BIO_snprintf() need to return error status -1. 0 will be
considered a correct return value, this may cause crash, please
refer to
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4075
Fake BIO_snprintf() need to return error status -1. 0 will be
considered a correct return value, this may cause crash, please
refer to
|
By
Li, Yi
·
#94119
·
|
|
Re: [PATCH] UsbNetworkPkg: add USB network devices support
[AMD Official Use Only - General]
Thanks Richard.
Please just send out the v2, I will give my feedback based on that.
Please run PatchCheck and Uncrustify on your patch before sending it out. Also,
[AMD Official Use Only - General]
Thanks Richard.
Please just send out the v2, I will give my feedback based on that.
Please run PatchCheck and Uncrustify on your patch before sending it out. Also,
|
By
Chang, Abner
·
#94118
·
|
|
File /Designs/2022/0923//How to add support for RISC-V in edk2 .pdf deleted
#file-notice
The following files and folders have been deleted from the Files area of the devel@edk2.groups.io group.
/Designs/2022/0923//How to add support for RISC-V in edk2 .pdf
By: Ni, Ray
The following files and folders have been deleted from the Files area of the devel@edk2.groups.io group.
/Designs/2022/0923//How to add support for RISC-V in edk2 .pdf
By: Ni, Ray
|
By
Group Notification <noreply@...>
·
#94117
·
|
|
Re: [PATCH v1 1/1] BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long
Create PR https://github.com/tianocore/edk2/pull/3378 for merge.
Create PR https://github.com/tianocore/edk2/pull/3378 for merge.
|
By
Bob Feng
·
#94116
·
|
|
Re: [PATCH v1 1/1] BaseTools: Edk2ToolsBuild: Fixing pipeline build due to path too long
Reviewed-by: Bob Feng <bob.c.feng@...>
Reviewed-by: Bob Feng <bob.c.feng@...>
|
By
Bob Feng
·
#94115
·
|
|
Re: [PATCH] MdeModulePkg/TerminalDxe: add modes
I spotted this issue when I wanted to use the largest possible text
mode in UEFI shell at high graphics resolutions. Is it not enough
reason for this commit?
Can you please elaborate this? I've tried
I spotted this issue when I wanted to use the largest possible text
mode in UEFI shell at high graphics resolutions. Is it not enough
reason for this commit?
Can you please elaborate this? I've tried
|
By
Konstantin Aladyshev
·
#94114
·
|
|
[PATCH] SecurityPkg: Remove enforcement of final GoIdle transition for CRB commands
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4077
Following the design described in the TCG specification,
the driver implementation of the CRB protocol does not require
enforcing completing
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4077
Following the design described in the TCG specification,
the driver implementation of the CRB protocol does not require
enforcing completing
|
By
Rodrigo Gonzalez del Cueto
·
#94113
·
|
|
Re: [PATCH 1/2] MdeModulePkg/UsbBusDxe: Avoid continuing on error path
Hello,
1. For “"Avoid continuing on error path" - The reset can happen before PortState is zero'd, so running this at the start of the function ensures it will”:
My take is that the execution
Hello,
1. For “"Avoid continuing on error path" - The reset can happen before PortState is zero'd, so running this at the start of the function ensures it will”:
My take is that the execution
|
By
Wu, Hao A
·
#94112
·
|
|
Re: [PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC
It's PR based on the patch. Have any concern, please also share for me.
https://github.com/tianocore/edk2/pull/3349
Thanks,
Gua
It's PR based on the patch. Have any concern, please also share for me.
https://github.com/tianocore/edk2/pull/3349
Thanks,
Gua
|
By
Guo, Gua
·
#94111
·
|
|
[PATCH v3 2/2] BaseTools/Plugin: Add coverage support for Unit Test
From: Gua Guo <gua.guo@...>
For GCC, use lcov to generate Unit Test code coverage
report
For VS2019, use OpenCppCoverage to generate code
coverage report
Cc: Liming Gao
From: Gua Guo <gua.guo@...>
For GCC, use lcov to generate Unit Test code coverage
report
For VS2019, use OpenCppCoverage to generate code
coverage report
Cc: Liming Gao
|
By
Guo, Gua
·
#94110
·
|
|
[PATCH v3 1/2] UnitTestFrameworkPkg: Add code coverage support for GCC
From: Gua Guo <gua.guo@...>
In order to collect code coverage after running executable
file, generate *.gcda and *.gcno file that require by lcov tool
to generate code coverage report.
Cc:
From: Gua Guo <gua.guo@...>
In order to collect code coverage after running executable
file, generate *.gcda and *.gcno file that require by lcov tool
to generate code coverage report.
Cc:
|
By
Guo, Gua
·
#94109
·
|
|
[PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC
From: Gua Guo <gua.guo@...>
V1: Add coverage option for GCC
V2: Add ReadMe.md for how to generate coverage report
V3: Add VS2019 and GCC code coverage support
Gua Guo (2):
From: Gua Guo <gua.guo@...>
V1: Add coverage option for GCC
V2: Add ReadMe.md for how to generate coverage report
V3: Add VS2019 and GCC code coverage support
Gua Guo (2):
|
By
Guo, Gua
·
#94108
·
|
|
[PATCH v2 1/1] MdeModulePkg/Core: Fix the potential hang of calling SetTimer.
When calling SetTimer with Type is not TimerCancel and TriggerTime is 0,
gTimer is used to get the timer period. However, gTimer is NULL before
EFI_TIMER_ARCH_PROTOCOL is installed. Adding the check
When calling SetTimer with Type is not TimerCancel and TriggerTime is 0,
gTimer is used to get the timer period. However, gTimer is NULL before
EFI_TIMER_ARCH_PROTOCOL is installed. Adding the check
|
By
Ying-Tsun Huang
·
#94107
·
|
|
[PATCH v2 0/1] MdeModulePkg/Core: Fix the potential hang of calling SetTimer.
When calling SetTimer with Type is not TimerCancel and TriggerTime is 0,
gTimer is used to get the timer period. However, gTimer is NULL before
EFI_TIMER_ARCH_PROTOCOL is installed. Adding the check
When calling SetTimer with Type is not TimerCancel and TriggerTime is 0,
gTimer is used to get the timer period. However, gTimer is NULL before
EFI_TIMER_ARCH_PROTOCOL is installed. Adding the check
|
By
Ying-Tsun Huang
·
#94106
·
|
|
[PATCH v2 1/1] OvmfPkg/PlatformInitLib: q35 mtrr setup fix
Traditional q35 memory layout is 2.75 GB of low memory, leaving room
for the pcie mmconfig at 0xb0000000 and the 32-bit pci mmio window at
0xc0000000. Because of that OVMF tags the memory range
Traditional q35 memory layout is 2.75 GB of low memory, leaving room
for the pcie mmconfig at 0xb0000000 and the 32-bit pci mmio window at
0xc0000000. Because of that OVMF tags the memory range
|
By
Gerd Hoffmann
·
#94105
·
|
|
Re: [PATCH V4 00/10] Introduce Lazy-accept for Tdx guest
Hi, Liming/Jian/Zhiguang/Michael
Can you help to review below patches for the lazy-accept feature? Because you're the maintainer/reviewer of the related modules.
Any comment is welcome.
[PATCH V4
Hi, Liming/Jian/Zhiguang/Michael
Can you help to review below patches for the lazy-accept feature? Because you're the maintainer/reviewer of the related modules.
Any comment is welcome.
[PATCH V4
|
By
Min Xu
·
#94104
·
|
|
Re: [PATCH] RedfishPkg/JsonLib: Fix JsonLib build failure
[AMD Official Use Only - General]
Reviewed-by: Abner Chang <abner.chang@...>
[AMD Official Use Only - General]
Reviewed-by: Abner Chang <abner.chang@...>
|
By
Chang, Abner
·
#94103
·
|
|
Re: [PATCH 1/1] OvmfPkg: Store PageTablePool in TdxWorkArea
Hi, Gerd
Do you have any comments on this patch?
Hi, Gerd
Do you have any comments on this patch?
|
By
Min Xu
·
#94102
·
|
|
Re: [PATCH V2 1/3] CryptoPkg: Add EC support
That change to OpensslLib.inf should not have been done either.
Looks like this EC feature needs more evaluation to fit into the
structured PCD control of the lib sizes.
Mike
That change to OpensslLib.inf should not have been done either.
Looks like this EC feature needs more evaluation to fit into the
structured PCD control of the lib sizes.
Mike
|
By
Michael D Kinney
·
#94101
·
|
|
Updated Event: EDKII Open Design Meeting - Friday, September 23, 2022
#cal-invite
EDKII Open Design Meeting
When:
Friday, September 23, 2022
9:30am to 10:00am
(UTC+08:00)
EDKII Open Design Meeting
When:
Friday, September 23, 2022
9:30am to 10:00am
(UTC+08:00)
|
By
Group Notification <noreply@...>
·
#94100
·
|