All of them including GCC 4.8 and 4.9?
Rebecca
On 11/22/2024 2:08 PM, Michael D Kinney via groups.io wrote:
Hi Rebecca,
Yes. I have collected feedback. I have found some use of these toolchains.
I do not have a date when the move to newer toolchains will be completed.
Mike
-Origina
On 10/22/2024 2:48 AM, Chao Li wrote:
I see the final licence in non-osi is GPL2.0, so it that allowed for
some people build the EmulatorDxe.efi into their FW and release it?
I believe it is allowed because tools like Fiano allow you to remove
drivers such as EmulatorDxe from the firmware ima
I'm still waiting for a review on this.
Andrei suggested we might want to have both versions available for
people to use, but unless there's a problem with the new version being
GPL I think replacing it makes more sense.
--
Rebecca
On 9/9/2024 10:10 AM, Rebecca Cran via group
On 9/6/2024 9:25 AM, Ard Biesheuvel via groups.io wrote:
arm64 firmware? Or RISC-V? There are many more options now for native
drivers on arm64, so I'd expect the relevance of this hack to diminish
but I guess RISC-V is at a different point on this curve.
arm64. The big thing that's missing is
Hi Andrei,
I've been talking to a few people about X86EmulatorPkg and their
experience with it hasn't been positive: apparently there are lots of
cases where it's failed to work (i.e. caused crashes) which is why it's
not been more widely used.
Since suggesting they try MultiArchUefiPkg the
We don't need AssignReviewers.yaml since there are no reviewers only
maintainers.
Otherwise it looks good.
--
Rebecca
On 9/4/2024 9:20 AM, Jayaprakash, N via groups.io wrote:
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4840
Migrate data from Maintainers.txt to the GitHub standard
Do the TF-A binaries in edk2-non-osi need updated for SbsaQemu?
With the binaries in Platform/Qemu/Sbsa I get the following error during
boot:
GetCpuCount: We have 4 cpus.
GetMpidr: MPIDR for CPU0: = 0
GetMpidr: MPIDR for CPU1: = 1
GetMpidr: MPIDR for CPU2: = 2
GetMpidr: MPIDR for CPU3: = 3
Ge
Also, leading underscores are supposed to be reserved for compiler
implementations (and there only needs to be a single trailing
underscore) so it should really be:
__CXL_Early_Discovery_TABLE_H__ -> CXL_EARLY_DISCOVERY_TABLE_H_
--
Rebecca
On 8/30/2024 12:06 PM, Michael D Kinney via groups.
On 8/13/2024 9:18 PM, Nhi Pham wrote:
+/**
+ This function updates the BMC information.
+
+ @param[in] VOID
+
+ @retval EFI_SUCCESS The entry point is executed successfully.
+ @retval Other Some error occurs when executing this entry point.
+
+**/
+EFI_STATUS
+UpdateBmcConfi
Work with upstream/community is done on my own time, so update my entry
to contain my personal email address.
Signed-off-by: Rebecca Cran
---
Maintainers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Maintainers.txt b/Maintainers.txt
index 824838486072..27f4056a6f49 100
Work with upstream/community is done on my own time, so update my entry
to contain my personal email address.
Signed-off-by: Rebecca Cran
---
Maintainers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Maintainers.txt b/Maintainers.txt
index 8248384860..27f4056a6f 100644
On 8/13/2024 9:33 PM, Nhi Pham via groups.io wrote:
This could be a static function.
+EFI_STATUS
+EFIAPI
+AcpiInstallSpmiTable (
+ VOID
+ );
+
#endif /* ACPI_PLATFORM_H_ */
diff --git a/Platform/Ampere/JadePkg/Drivers/AcpiPlatformDxe/AcpiPlatformDxe.c
b/Platform/Ampere/JadePkg/Drivers/AcpiPl
Reviewed-by: Rebecca Cran
On 8/8/2024 9:12 PM, Nhi Pham wrote:
From: Tam Chi Nguyen
Currently, the NVRAM FV region is only updated once at FlashPei that makes
the data in NVRAM FV outdated with data in NVRAM region in SPI-NOR.
It causes the duplication of the valid NV variables when the Vari
For the series:
Reviewed-by: Rebecca Cran
I see this is marked as an RFC, but I think it's a change that should be
committed.
--
Rebecca
On 7/29/24 06:22, Ard Biesheuvel wrote:
From: Ard Biesheuvel
The original EDK2 port to 32-bit ARM supported multi-core but on today's
ARM systems, only
On 7/26/24 11:37, Michael D Kinney via groups.io wrote:
Members with more than one email address is confusing. Can we
limit to single email address for TianoCore activities?
Also, should Maintainer.txt be removed yet? There is a GitHub
Action active in edk2 now that assigns reviews from Maint
On 6/5/2024 4:21 PM, Michael D Kinney via groups.io wrote:
* Some PRs have been merged using the "Rebase and Merge" button in the
PR after all required reviews completed and all CI checks pass. Instead,
the "push" label should continue to be used. There does not appear to be
any unexpect
Reviewed-by: Rebecca Cran
--
Rebecca Cran
On 6/4/2024 6:57 PM, Nhi Pham wrote:
This allows to initialize secure boot with the default factory keys
embedded in firmware flash image.
For example, to incorporate PK, KEK, and DB default keys, specify the
corresponding key files in the Jade.dsc as
On 1/23/2024 7:10 AM, Sami Mujawar wrote:
@@ -310,6 +318,7 @@ GenericWatchdogEntry (
{
EFI_STATUS Status;
EFI_HANDLE Handle;
+ UINT32 WatchdogIId;
[SAMI] Minor, the above variable name should be WatchdogIid to comply with the
coding standard.
I was wondering about the naming, since it's the "
On 1/22/2024 6:53 PM, Oliver Smith-Denny wrote:
I was able to repro your bug (by just turning on page guards on
ArmVirtQemu, allocating runtime mem and freeing it). I think you
are the first person to free runtime mem on ARM64 with page guards
enabled (and to care when it failed :).
The heap gu
On 1/19/2024 1:03 PM, Oliver Smith-Denny wrote:
Thanks for trying. In lieu of being able to test myself, all I can offer
is adding some more prints, when the memory gets allocated, making sure
it is 64k aligned then. I'd be curious to see what the address is that
is attempting to be freed.
My g
On 1/18/2024 12:26 PM, Oliver Smith-Denny wrote:
Does this solve your issue? I have to run to a meeting, but I can
write this in actual patch form (and give it a quick test) later.
Unfortunately that didn't work: I still get the assert.
...
SmbiosCreate64BitTable() re-allocate SMBIOS 64-bit t
Fixes and improvements to GenericWatchdogDxe.
PR: https://github.com/tianocore/edk2/pull/5176
Changes between v3 and v4:
- Check Interface Identification Register for architecture revision before
setting the high offset register value.
- Use @par for reference.
- Move setting of EBS flag from
The calculation of the timer period was broken. Introduce a global
mTimerPeriod so the calculation can be removed. Since mTimerFrequencyHz
is only used in one place, remove the global and make it a local
variable. Do the same with mNumTimerTicks.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/Ge
The generic watchdog offset register is 48 bits wide, and can be set by
performing two 32-bit writes.
Add support for writing the high 16 bits of the offset register and
update the signature of the WatchdogWriteOffsetRegister function to take
a UINT64 value.
Signed-off-by: Rebecca Cran
---
ArmP
Update GenericWatchdogDxe to disable watchdog interaction after exiting
boot services. Also, move the mEfiExitBootServicesEvent event to the top
of the file with the other static variables.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.c | 17 ++
On 1/5/2024 1:26 AM, Ard Biesheuvel wrote:
@@ -91,7 +88,8 @@ WatchdogExitBootServicesEvent (
)
{
WatchdogDisable ();
- mNumTimerTicks = 0;
+ mTimerPeriod= 0;
+ mExitedBootServices = TRUE;
Where is this declared/defined?
Oh, it's defined in the 3rd patch - which obviously
On 1/5/2024 4:12 AM, Sami Mujawar wrote:
- // if TimerPeriod is 0, this is a request to stop the watchdog.
+ // If we've exited Boot Services but TimerPeriod isn't zero, this
+ // indicates that the caller is doing something wrong.
+ if (mExitedBootServices && (TimerPeriod != 0)) {
[SAMI] Thanks
On 1/18/2024 12:04 PM, Oliver Smith-Denny wrote:
On 1/18/2024 10:45 AM, Rebecca Cran via groups.io wrote:
No, I mean SbsaQemu from edk2-platforms:
https://github.com/tianocore/edk2-platforms/tree/master/Platform/Qemu/SbsaQemu
Sure, if you can repro there that is helpful.
I've realiz
On 1/18/2024 11:38 AM, Oliver Smith-Denny wrote:
Yeah, if you can get it running there, that would be a good data point.
I assume you mean the Project Mu QemuSbsaPkg? If so that is great, but
you will need to update the RUNTIME_PAGE_ALLOCATION_GRANULARITY back to
0x1. It was set to 0x1000 fo
On 1/18/2024 9:48 AM, Oliver Smith-Denny via groups.io wrote:
Are you including this commit:
https://github.com/tianocore/edk2/commit/00b51e0d78a547dd78119ec44fcc74a01b6f79c8?
Can you share some more details on where this is failing? I.e. what
assert is getting tripped? Presumably without Heap
I've been debugging an assert failure when using HeapGuard on AArch64. A
call to FreePages in SmbiosDxe is failing because the memory is aligned
to 0x1000 instead of 0x1 as defined by
RUNTIME_PAGE_ALLOCATION_GRANULARITY.
I'm enabling HeapGuard by setting the PCDs to the following values:
On 1/5/2024 1:26 AM, Ard Biesheuvel via groups.io wrote:
On Fri, 5 Jan 2024 at 06:15, Rebecca Cran
wrote:
Fixes and improvements to GenericWatchdogDxe.
What is the difference between v2 and v3?
Sorry, I should have said that. I forgot to build v2 and it had a bug in
the exit boot service
The generic watchdog offset register is 48 bits wide, and can be set by
performing two 32-bit writes.
Add support for writing the high 16 bits of the offset register and
update the signature of the WatchdogWriteOffsetRegister function to take
a UINT64 value.
Signed-off-by: Rebecca Cran
---
ArmP
The calculation of the timer period was broken. Introduce a global
mTimerPeriod so the calculation can be removed. Since mTimerFrequencyHz
is only used in one place, remove the global and make it a local
variable. Do the same with mNumTimerTicks.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/Ge
Fixes and improvements to GenericWatchdogDxe.
PR: https://github.com/tianocore/edk2/pull/5176
Rebecca Cran (3):
ArmPkg: Update GenericWatchdogDxe to allow setting full 48-bit offset
ArmPkg: Introduce global mTimerPeriod and remove calculation
ArmPkg: Disable watchdog interaction after exiti
Update GenericWatchdogDxe to disable watchdog interaction after exiting
boot services. Also, move the mEfiExitBootServicesEvent event to the top
of the file with the other static variables.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.c | 14 +++---
Thanks, I've incorporated the changes into the v2 patch series.
--
Rebecca
On 1/3/2024 3:56 PM, Ard Biesheuvel wrote:
Hi Rebecca,
On Wed, 3 Jan 2024 at 21:44, Rebecca Cran
wrote:
Fix the calculation of the timer period in GenericWatchdogDxe: we need
to multiply before dividing to keep the v
Thanks, I've incorporated the changes into the v2 patch series.
--
Rebecca
On 1/4/2024 3:01 AM, Sami Mujawar wrote:
Hi Rebecca,
Thank you for this patch.
I have some minor suggestions marked inline as [SAMI].
Regards,
Sami Mujawar
On 03/01/2024, 20:44, "Rebecca Cran" mailto:rebe...@os
The calculation of the timer period was broken. Introduce a global
mTimerPeriod so the calculation can be removed. Since mTimerFrequencyHz
is only used in one place, remove the global and make it a local
variable. Do the same with mNumTimerTicks.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/Ge
Update GenericWatchdogDxe to disable watchdog interaction after exiting
boot services. Also, move the mEfiExitBootServicesEvent event to the top
of the file with the other static variables.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.c | 14 +++---
Fixes and improvements to GenericWatchdogDxe.
PR: https://github.com/tianocore/edk2/pull/5176
Rebecca Cran (3):
ArmPkg: Update GenericWatchdogDxe to allow setting full 48-bit offset
ArmPkg: Introduce global mTimerPeriod and remove calculation
ArmPkg: Disable watchdog interaction after exiti
The generic watchdog offset register is 48 bits wide, and can be set by
performing two 32-bit writes.
Add support for writing the high 16 bits of the offset register and
update the signature of the WatchdogWriteOffsetRegister function to take
a UINT64 value.
Signed-off-by: Rebecca Cran
---
ArmP
I noticed recent commits by Jeff Brasen, Jake Garver, Joey Vagades and
Michael Roth have funky Author lines, which I think means .mailmap needs
updated?
commit 7a5823f85be99b9a92751fcf4141f7982fa5cc80
Author: Jeff Brasen via groups.io
Date: Thu Dec 28 12:47:08 2023 -0800
EmbeddedPkg: Ad
Wouldn't it be better to add the Stack Protector library
(MdePkg/Library/BaseStackCheckLib/BaseStackCheckLib.inf) instead of
disabling it?
--
Rebecca Cran
On 1/4/2024 11:49 AM, Prabin CA via groups.io wrote:
Add the no-stack-protector compiler flag to allow StandaloneMM builds
on both AArch6
Fix the calculation of the timer period in GenericWatchdogDxe: we need
to multiply before dividing to keep the values as integers.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ArmPkg
Update GenericWatchdogDxe to disable watchdog interaction after exiting
boot services. Also, move the mEfiExitBootServicesEvent event to the top
of the file with the other static variables.
Signed-off-by: Rebecca Cran
---
ArmPkg/Drivers/GenericWatchdogDxe/GenericWatchdogDxe.c | 14 +-
The generic watchdog offset register is 48 bits wide, and can be set by
performing two 32-bit writes.
Add support for writing the high 16 bits of the offset register and
update the signature of the WatchdogWriteOffsetRegister function to take
a UINT64 value.
Signed-off-by: Rebecca Cran
---
ArmP
Fixes and improvements to GenericWatchdogDxe.
PR: https://github.com/tianocore/edk2/pull/5176
Rebecca Cran (3):
ArmPkg: Update GenericWatchdogDxe to allow setting full 48-bit offset
ArmPkg: Fix the calculation of the timer period in GenericWatchdogDxe
ArmPkg: Disable watchdog interaction af
On 12/8/2023 5:19 PM, Rebecca Cran wrote:
Add the new DEBUG_MANAGEABILITY debug level to MdePkg.dec and MdePkg.uni.
Improve the wording of the description of the DEBUG_MANAGEABILITY level in
DebugLib.h.
Update the comment block in ArmVirtPkg.dsc.inc with the new list and updated
formatting.
P
Update the debug level comments in ArmVirt.dsc.inc to sync with
MdePkg/Include/Library/DebugLib.h.
Signed-off-by: Rebecca Cran
---
ArmVirtPkg/ArmVirt.dsc.inc | 42 ++--
1 file changed, 22 insertions(+), 20 deletions(-)
diff --git a/ArmVirtPkg/ArmVirt.dsc.inc b/ArmVirtPkg/ArmVirt
Update MdePkg.dec to add the manageability debug level to
PcdFixedDebugPrintErrorLevel.
Signed-off-by: Rebecca Cran
---
MdePkg/MdePkg.dec | 1 +
1 file changed, 1 insertion(+)
diff --git a/MdePkg/MdePkg.dec b/MdePkg/MdePkg.dec
index ac54338089e8..bec63f5416e2 100644
--- a/MdePkg/MdePkg.dec
+++
Add the new DEBUG_MANAGEABILITY debug level to MdePkg.dec and MdePkg.uni.
Improve the wording of the description of the DEBUG_MANAGEABILITY level in
DebugLib.h.
Update the comment block in ArmVirtPkg.dsc.inc with the new list and updated
formatting.
Rebecca Cran (4):
MdePkg: Improve wording o
Update MdePkg.uni with the manageability debug level.
Signed-off-by: Rebecca Cran
---
MdePkg/MdePkg.uni | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MdePkg/MdePkg.uni b/MdePkg/MdePkg.uni
index 5c1fa24065c7..75dbc6ffe3c0 100644
--- a/MdePkg/MdePkg.uni
+++ b/MdePkg/MdePkg.uni
@@ -214,6 +2
Improve the wording of the comment explaining the DEBUG_MANAGEABILITY
debug level.
Signed-off-by: Rebecca Cran
---
MdePkg/Include/Library/DebugLib.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MdePkg/Include/Library/DebugLib.h
b/MdePkg/Include/Library/DebugLib.h
inde
On 11/14/2023 7:51 AM, Laszlo Ersek via groups.io wrote:
Funnily enough, my stance is quite the opposite. I happen to disagree
with some patterns that uncrustify enforces, but I'm thankful that at
any given state of CI (= using any given version of uncrustify), we
can't have any more debates abo
On 11/13/2023 5:29 AM, Marcin Juszkiewicz via groups.io wrote:
Still a fan of adding edk2-uncrustify to BaseTools. If we are expected
to use it then let it get installed at same moment as "build" command is.
The issue with doing this is there's a push to remove all C/C++ code
from BaseTools (
On 10/27/2023 9:15 AM, Joey Vagedes via groups.io wrote:
Upgrades edk2-pytool-library to v0.19.3 and edk2-pytool-extensions to v0.25.1
and performs all necessary integrations as noted in the individual package
commits.
Cc: Sean Brogan
Cc: Michael Kubacki
Cc: Michael D Kinney
Cc: Liming Gao
On 10/17/2023 4:05 AM, Laszlo Ersek wrote:
Nhi says that reading LINK_CONTROL_LINK_STATUS_REG is redundant; its only
use was debugging (before commit 380b4b40c60d). Thus, we can go farther
than commit 2e27c62ef000, and remove the MmioRead32() call altogether.
Build-tested with "Jade.dsc".
Cc: C
On 9/25/2023 3:03 AM, Marcin Juszkiewicz via groups.io wrote:
I feel sick each time I have to edit EDK2 code.
All those INF, DEC, DSC, FDF, XYZ files are something I do not even try
to understand, just got minimal knowledge what goes where by asking Leif
(thanks a lot!) and observing build error
On 9/20/2023 9:55 AM, Marcin Juszkiewicz via groups.io wrote:
Those changes float around whenever I do some changes in code. Time to
send them for merge and stop bothering.
Marcin Juszkiewicz (2):
Silicon/SbsaQemu: drop duplicated Pcd
Silicon/SbsaQemu: fix comment to show proper table name
Improve the Readme.md in Platform/Ampere:
Direct people to the top-level Readme.md file for build instructions.
Mention the edk2-ampere-tools repo for additional build tools.
Delete everything else, since it's redundant.
Signed-off-by: Rebecca Cran
---
Platform/Ampere/Readme.md | 29 ++-
On 9/12/2023 10:04 AM, CrossedCarpet via groups.io wrote:
Greetings,
As newer laptops start lacking Ethernet ports, I started investigating
the possibility of using *USB Tethering* as a replacement, to *allow for
internet connection at boot*.
Current attempts at employing *ifconfig* to configur
On 9/12/2023 3:58 AM, Leif Lindholm via groups.io wrote:
So, it's really good that you add "known good" versions so that if
someone runs into a problem around toolchain version compatibility,
they know what to use. But anything in edk2-platform should be kept up
to date so that it builds on curr
Improve the Readme.md in Platform/Ampere:
- At this point eMAG is irrelevant, and most people are likely
using Altra systems. Drop mention of it.
- Instead of mentioning the 'latest' versions of CentOS and Ubuntu
(which will by definition change over time), specify Ubuntu 22.04
and CentOS 7.
On 9/7/2023 9:46 AM, Nhi Pham wrote:
This adds Rebecca Cran as reviewer, updates myself as maintainer, and
Leif as reviewer. Also, removes Vu Nguyen and Thang Nguyen due to no
longer working on EDK2.
Signed-off-by: Nhi Pham
---
Maintainers.txt | 7 +++
1 file changed, 3 insertions(+), 4
On 9/6/2023 11:29 AM, Michael Kubacki via groups.io wrote:
From: Michael Kubacki
The include guard is incomplete and does not define the macro.
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Zhiguang Liu
Cc: Rebecca Cran
Signed-off-by: Michael Kubacki
---
MdePkg/Library/BaseRngLib/BaseRngLibIn
On 2019-04-11 11:52, Laszlo Ersek wrote:
On 04/11/19 16:23, Philippe Mathieu-Daudé wrote:
On 4/11/19 5:16 AM, Rebecca Cran via Groups.Io wrote:
Some systems such as FreeBSD identify the platform as 'arm64'
and not 'aarch64' as Linux does.
Per https://bugs.freebsd.org/bugz
On 2019-04-11 11:35, Laszlo Ersek wrote:
On 04/11/19 16:32, Philippe Mathieu-Daudé wrote:
Rebecca: do you remember if you modified something in your profile?
How are you sending your patches to the list?
Sorry you became our 'patches via groups.io' guinea pig ;)
Yes, I've changed those field
On 2019-04-10 20:07, Rebecca Cran via Groups.Io wrote:
Thanks. I'm working on fixing it now: it looks like it needs new
compiler flags in BaseTools/Source/C/Makefiles/header.makefile, as
well as recognizing arm64 as a platform name in addition to aarch64
It didn't need any com
Some systems such as FreeBSD identify the platform as 'arm64'
and not 'aarch64' as Linux does.
Signed-off-by: Rebecca Cran
---
BaseTools/Source/C/GNUmakefile | 5 +++--
BaseTools/Source/C/Makefiles/header.makefile | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --
On 2019-04-10 18:09, Liming Gao wrote:
Yes. No test on FreeBSD. If possible, can you contribute the patch to fix this
issue on FreeBSD?
Thanks. I'm working on fixing it now: it looks like it needs new
compiler flags in BaseTools/Source/C/Makefiles/header.makefile, as well
as recognizing ar
On 2019-04-10 08:41, Philippe Mathieu-Daudé wrote:
This doesn't look like an architecture problem. It seems your GCC
version isn't checked correctly by BaseTools. This warning is supposed
to be disabled, see:
StdLib/LibC/Stdio/Stdio.inf: GCC:*_*_*_CC_FLAGS= -fno-builtin
-Wno-pointer-to-int
Is there any expectation that EDK2 will build on non-x86 systems?
I tried building BaseTools (from git master,
ae2fb9ead47b5abaf2a4e815b5f57c8f4838b221) using GCC 8.2 on a SoftIron
OverDrive 1000 (running FreeBSD) but there are lots of errors, such as:
gcc -c -I .. -I ../Include/Common -I
Fix a few typos in LegacyBiosBuildE820, and improve the debug output of
the E820 table to pad with zeros instead of spaces, remove extra hyphens
and display the memory type in decimal.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Rebecca Cran
---
.../Csm/LegacyBiosDxe/L
74 matches
Mail list logo
