* [Buildroot] [PATCH v2 1/3] configs/qemu_aarch64_sbsa_defconfig: update ATF to v2.11
@ 2024-10-27 19:43 Romain Naour via buildroot
2024-10-27 19:43 ` [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 Romain Naour via buildroot
2024-10-27 19:43 ` [Buildroot] [PATCH v2 3/3] configs/qemu_aarch64_sbsa_defconfig: switch to neoverse-n1 (armv8.2a) Romain Naour via buildroot
0 siblings, 2 replies; 7+ messages in thread
From: Romain Naour via buildroot @ 2024-10-27 19:43 UTC (permalink / raw)
To: buildroot; +Cc: Romain Naour
qemu_aarch64_sbsa_defconfig doesn't boot since the qemu version bump to
9.0 [1]. Sync the ATF version with the one (v2.11) used by Qemu tests
[2].
Since we use a released version of ATF, we switch to ATF custom version
to use the official ATF repository instead of the read-only mirror on
ARM-software's github.
This doesn't fix yet this defconfig due to a bug in edk2 as mentioned
in the qemu commit log [2].
With the edk2 version bump applied, this defconfig doesn't boot with
ATF v2.10-lts but boot successfully with ATF v2.11.
[1] https://gitlab.com/buildroot.org/buildroot/-/commit/103a55028c75dace312470ba05a197886c6b6100
[2] https://gitlab.com/qemu-project/qemu/-/commit/24a7cd6a7c21f82f1ce9bd5ecf6fb54eb7bf4602
Signed-off-by: Romain Naour <romain.naour@smile.fr>
---
v2: add missing hash board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash
arm-trusted-firmware-v2.7-git4.tar.gz is not removed since it still used by
qemu_arm_vexpress_tz_defconfig
---
.../patches/arm-trusted-firmware/arm-trusted-firmware.hash | 1 +
configs/qemu_aarch64_sbsa_defconfig | 5 ++---
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash b/board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash
index 5632db01f8..4a0534d1ba 100644
--- a/board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash
+++ b/board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash
@@ -1,3 +1,4 @@
# Locally computed:
sha256 c9f0d0bf967d690edbf34b621728a6271856f2e26ed46081a285b6d627a358c5 arm-trusted-firmware-v2.7-git4.tar.gz
sha256 7efa89e1b4e4106ee05d68e876c8efbb146364d89cfd5d26bf4647b09c08f32b arm-trusted-firmware-v2.10-git4.tar.gz
+sha256 c0f23ccc71c49989e9ad238acf334473c17b7c88f79a20c829c3d443e3794a22 arm-trusted-firmware-v2.11-git4.tar.gz
diff --git a/configs/qemu_aarch64_sbsa_defconfig b/configs/qemu_aarch64_sbsa_defconfig
index 8da4331b30..23d274b529 100644
--- a/configs/qemu_aarch64_sbsa_defconfig
+++ b/configs/qemu_aarch64_sbsa_defconfig
@@ -17,9 +17,8 @@ BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_SIZE="128M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/ARM-software/arm-trusted-firmware.git"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="v2.7"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION=y
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE="v2.11"
BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="qemu_sbsa"
BR2_TARGET_ARM_TRUSTED_FIRMWARE_FIP=y
BR2_TARGET_EDK2=y
--
2.45.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply related [flat|nested] 7+ messages in thread* [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 2024-10-27 19:43 [Buildroot] [PATCH v2 1/3] configs/qemu_aarch64_sbsa_defconfig: update ATF to v2.11 Romain Naour via buildroot @ 2024-10-27 19:43 ` Romain Naour via buildroot 2024-10-28 20:27 ` Julien Olivain 2024-10-27 19:43 ` [Buildroot] [PATCH v2 3/3] configs/qemu_aarch64_sbsa_defconfig: switch to neoverse-n1 (armv8.2a) Romain Naour via buildroot 1 sibling, 1 reply; 7+ messages in thread From: Romain Naour via buildroot @ 2024-10-27 19:43 UTC (permalink / raw) To: buildroot; +Cc: Romain Naour Release notes: https://github.com/tianocore/edk2/releases/tag/edk2-stable202405 We can't bump to edk2-stable202408 yet due to a runtime issue while testing qemu_aarch64_sbsa_defconfig following the switch generic ArmPsciResetSystemLib [1] ERROR: sbsa_sip_smc_handler: unhandled SMC (0xc20000ca) (function id: 202) Qemu 9.0/9.1 is using a slightly older edk2 firmware based on edk2-stable202405 release [2] that contains a commit [3] fixing a bootloader crash produced with qemu_aarch64_sbsa_defconfig [4] since Qemu 9.0. From [5]: "The version of the sbsa-ref EDK2 firmware we used to use in this test had a bug where it might make an unaligned access to the framebuffer, which causes a guest crash on newer versions of QEMU where we enforce the architectural requirement that unaligned accesses to Device memory should take an exception." This commit [5] is backported to edk2-stable202405. For the same reason, we have to update edk2-platforms to a specific version [6]: "QemuSbsa: enable WriteCombine for the FrameBuffer QEMU no longer permits misaligned access to device memory, which breaks QemuVideoDxe on SbsaQemu. c1d1910be6e04a8b1a73090cf2881fb698947a6e commit in EDK2 fixed it by enabling WriteCombine for Framebuffer memory. This change enables that fix." [1] https://github.com/tianocore/edk2-platforms/commit/2d0668d399708fc242336e310cc7e7bec0aec891 [2] https://gitlab.com/qemu-project/qemu/-/commit/24a7cd6a7c21f82f1ce9bd5ecf6fb54eb7bf4602 [3] https://github.com/tianocore/edk2/commit/c1d1910be6e04a8b1a73090cf2881fb698947a6e [4] https://gitlab.com/buildroot.org/buildroot/-/jobs/7764483764 [5] https://gitlab.com/qemu-project/qemu/-/commit/6c84daac58f0d75a908626faf89a832fc0532140 [6] https://github.com/tianocore/edk2-platforms/commit/3f08401365d67e10924c774e6c3f64be56bc15b6 Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/7764483764 Signed-off-by: Romain Naour <romain.naour@smile.fr> Cc: Waldemar Brodkorb <wbx@openadk.org> --- ...oDxe-add-feature-PCD-to-remap-frameb.patch | 129 ++++++++++++++++++ boot/edk2/edk2.hash | 2 +- boot/edk2/edk2.mk | 2 +- package/edk2-platforms/edk2-platforms.hash | 2 +- package/edk2-platforms/edk2-platforms.mk | 2 +- 5 files changed, 133 insertions(+), 4 deletions(-) create mode 100644 boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch diff --git a/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch b/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch new file mode 100644 index 0000000000..5f6ceb289d --- /dev/null +++ b/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch @@ -0,0 +1,129 @@ +From 921c78f57a16b00debd58899a48e7045015c374b Mon Sep 17 00:00:00 2001 +From: Ard Biesheuvel <ardb@kernel.org> +Date: Mon, 17 Jun 2024 17:07:41 +0200 +Subject: [PATCH] OvmfPkg/QemuVideoDxe: add feature PCD to remap framebuffer + W/C + +Some platforms (such as SBSA-QEMU on recent builds of the emulator) only +tolerate misaligned accesses to normal memory, and raise alignment +faults on such accesses to device memory, which is the default for PCIe +MMIO BARs. + +When emulating a PCIe graphics controller, the framebuffer is typically +exposed via a MMIO BAR, while the disposition of the region is closer to +memory (no side effects on reads or writes, except for the changing +picture on the screen; direct random access to any pixel in the image). + +In order to permit the use of such controllers on platforms that only +tolerate these types of accesses for normal memory, it is necessary to +remap the memory. Use the DXE services to set the desired capabilities +and attributes. + +Hide this behavior under a feature PCD so only platforms that really +need it can enable it. (OVMF on x86 has no need for this) + +Signed-off-by: Ard Biesheuvel <ardb@kernel.org> +Upstream: https://github.com/tianocore/edk2/commit/c1d1910be6e04a8b1a73090cf2881fb698947a6e +Signed-off-by: Romain Naour <romain.naour@smile.fr> +--- + OvmfPkg/OvmfPkg.dec | 5 +++++ + OvmfPkg/QemuVideoDxe/Gop.c | 19 +++++++++++++++++++ + OvmfPkg/QemuVideoDxe/Qemu.h | 2 +- + OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf | 4 ++++ + 4 files changed, 29 insertions(+), 1 deletion(-) + +diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec +index 51be9a5959..2c40de8a13 100644 +--- a/OvmfPkg/OvmfPkg.dec ++++ b/OvmfPkg/OvmfPkg.dec +@@ -444,3 +444,8 @@ + + ## This feature flag indicates the firmware build supports secure boot. + gUefiOvmfPkgTokenSpaceGuid.PcdSecureBootSupported|FALSE|BOOLEAN|0x6d ++ ++ ## Whether QemuVideoDxe should perform a EFI_MEMORY_WC remap of the PCI ++ # framebuffer. This might be required on platforms that do not tolerate ++ # misaligned accesses otherwise. ++ gUefiOvmfPkgTokenSpaceGuid.PcdRemapFrameBufferWriteCombine|FALSE|BOOLEAN|0x75 +diff --git a/OvmfPkg/QemuVideoDxe/Gop.c b/OvmfPkg/QemuVideoDxe/Gop.c +index b11eed7558..a29c025afd 100644 +--- a/OvmfPkg/QemuVideoDxe/Gop.c ++++ b/OvmfPkg/QemuVideoDxe/Gop.c +@@ -9,6 +9,8 @@ + + #include "Qemu.h" + ++#include <Library/DxeServicesTableLib.h> ++ + STATIC + VOID + QemuVideoCompleteModeInfo ( +@@ -54,6 +56,7 @@ QemuVideoCompleteModeData ( + EFI_GRAPHICS_OUTPUT_MODE_INFORMATION *Info; + EFI_ACPI_ADDRESS_SPACE_DESCRIPTOR *FrameBufDesc; + QEMU_VIDEO_MODE_DATA *ModeData; ++ EFI_STATUS Status; + + ModeData = &Private->ModeData[Mode->Mode]; + Info = Mode->Info; +@@ -79,6 +82,22 @@ QemuVideoCompleteModeData ( + (UINT64)Mode->FrameBufferSize + )); + ++ if (FeaturePcdGet (PcdRemapFrameBufferWriteCombine)) { ++ Status = gDS->SetMemorySpaceCapabilities ( ++ FrameBufDesc->AddrRangeMin, ++ FrameBufDesc->AddrLen, ++ EFI_MEMORY_UC | EFI_MEMORY_WC | EFI_MEMORY_XP ++ ); ++ ASSERT_EFI_ERROR (Status); ++ ++ Status = gDS->SetMemorySpaceAttributes ( ++ FrameBufDesc->AddrRangeMin, ++ FrameBufDesc->AddrLen, ++ EFI_MEMORY_WC | EFI_MEMORY_XP ++ ); ++ ASSERT_EFI_ERROR (Status); ++ } ++ + FreePool (FrameBufDesc); + return EFI_SUCCESS; + } +diff --git a/OvmfPkg/QemuVideoDxe/Qemu.h b/OvmfPkg/QemuVideoDxe/Qemu.h +index 57341a0bbf..a3da725fbf 100644 +--- a/OvmfPkg/QemuVideoDxe/Qemu.h ++++ b/OvmfPkg/QemuVideoDxe/Qemu.h +@@ -13,7 +13,7 @@ + #ifndef _QEMU_H_ + #define _QEMU_H_ + +-#include <Uefi.h> ++#include <PiDxe.h> + #include <Protocol/GraphicsOutput.h> + #include <Protocol/PciIo.h> + #include <Protocol/DriverSupportedEfiVersion.h> +diff --git a/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf b/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf +index 43a6e07faa..4c0870171b 100644 +--- a/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf ++++ b/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf +@@ -44,6 +44,7 @@ + + [LibraryClasses] + BaseMemoryLib ++ DxeServicesTableLib + FrameBufferBltLib + DebugLib + DevicePathLib +@@ -61,6 +62,9 @@ + gEfiDevicePathProtocolGuid # PROTOCOL BY_START + gEfiPciIoProtocolGuid # PROTOCOL TO_START + ++[FeaturePcd] ++ gUefiOvmfPkgTokenSpaceGuid.PcdRemapFrameBufferWriteCombine ++ + [Pcd] + gUefiOvmfPkgTokenSpaceGuid.PcdOvmfHostBridgePciDevId + gUefiOvmfPkgTokenSpaceGuid.PcdVideoResolutionSource +-- +2.45.0 + diff --git a/boot/edk2/edk2.hash b/boot/edk2/edk2.hash index f7daa8ddf3..abcf3c6b8e 100644 --- a/boot/edk2/edk2.hash +++ b/boot/edk2/edk2.hash @@ -1,3 +1,3 @@ # Locally calculated -sha256 6bdfdffcc2235a117b3f9d4124da63103f19ff30157673f812e1093b20ebb7ad edk2-edk2-stable202308-git4.tar.gz +sha256 4595b9d9d14c06bd03f575e4b7623574a4a874ef465652ecdc224099a5b14fc7 edk2-edk2-stable202405-git4.tar.gz sha256 50ce20c9cfdb0e19ee34fe0a51fc0afe961f743697b068359ab2f862b494df80 License.txt diff --git a/boot/edk2/edk2.mk b/boot/edk2/edk2.mk index e5816b353a..145a9a80ae 100644 --- a/boot/edk2/edk2.mk +++ b/boot/edk2/edk2.mk @@ -4,7 +4,7 @@ # ################################################################################ -EDK2_VERSION = edk2-stable202308 +EDK2_VERSION = edk2-stable202405 EDK2_SITE = https://github.com/tianocore/edk2 EDK2_SITE_METHOD = git EDK2_LICENSE = BSD-2-Clause-Patent diff --git a/package/edk2-platforms/edk2-platforms.hash b/package/edk2-platforms/edk2-platforms.hash index 4c74c7dfb6..0095d4298d 100644 --- a/package/edk2-platforms/edk2-platforms.hash +++ b/package/edk2-platforms/edk2-platforms.hash @@ -1,3 +1,3 @@ # Locally calculated -sha256 c240a8ec7816bc5963d881c84eb18d880e9269c117cfc46a3106b0c5e6e80c66 edk2-platforms-e509ac5a729ebe2a3bc905aed1df23226aca4dc9.tar.gz +sha256 41fa720ac644ec0523c576ff28eba5e0308c9649111ce42f7d408b8d8b30eaf5 edk2-platforms-3f08401365d67e10924c774e6c3f64be56bc15b6.tar.gz sha256 50ce20c9cfdb0e19ee34fe0a51fc0afe961f743697b068359ab2f862b494df80 License.txt diff --git a/package/edk2-platforms/edk2-platforms.mk b/package/edk2-platforms/edk2-platforms.mk index 7bd86ff159..23d9221649 100644 --- a/package/edk2-platforms/edk2-platforms.mk +++ b/package/edk2-platforms/edk2-platforms.mk @@ -5,7 +5,7 @@ ################################################################################ # Keep in sync with latest commit as of the release date for boot/edk2 -EDK2_PLATFORMS_VERSION = e509ac5a729ebe2a3bc905aed1df23226aca4dc9 +EDK2_PLATFORMS_VERSION = 3f08401365d67e10924c774e6c3f64be56bc15b6 EDK2_PLATFORMS_SITE = $(call github,tianocore,edk2-platforms,$(EDK2_PLATFORMS_VERSION)) EDK2_PLATFORMS_LICENSE = BSD-2-Clause-Patent EDK2_PLATFORMS_LICENSE_FILES = License.txt -- 2.45.0 _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 2024-10-27 19:43 ` [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 Romain Naour via buildroot @ 2024-10-28 20:27 ` Julien Olivain 2024-10-28 21:12 ` Thomas Petazzoni via buildroot 0 siblings, 1 reply; 7+ messages in thread From: Julien Olivain @ 2024-10-28 20:27 UTC (permalink / raw) To: Romain Naour; +Cc: buildroot Hi Romain, Thank you for the patch! On 27/10/2024 20:43, Romain Naour via buildroot wrote: > Release notes: > > https://github.com/tianocore/edk2/releases/tag/edk2-stable202405 > > We can't bump to edk2-stable202408 yet due to a runtime issue while > testing qemu_aarch64_sbsa_defconfig following the switch generic > ArmPsciResetSystemLib [1] > > ERROR: sbsa_sip_smc_handler: unhandled SMC (0xc20000ca) (function > id: 202) > > Qemu 9.0/9.1 is using a slightly older edk2 firmware based on > edk2-stable202405 release [2] that contains a commit [3] fixing a > bootloader crash produced with qemu_aarch64_sbsa_defconfig [4] since > Qemu 9.0. > > From [5]: > "The version of the sbsa-ref EDK2 firmware we used to use in this test > had a bug where it might make an unaligned access to the framebuffer, > which causes a guest crash on newer versions of QEMU where we enforce > the architectural requirement that unaligned accesses to Device memory > should take an exception." > > This commit [5] is backported to edk2-stable202405. > > For the same reason, we have to update edk2-platforms to a specific > version [6]: > > "QemuSbsa: enable WriteCombine for the FrameBuffer > QEMU no longer permits misaligned access to device memory, which breaks > QemuVideoDxe on SbsaQemu. > > c1d1910be6e04a8b1a73090cf2881fb698947a6e commit in EDK2 fixed it by > enabling WriteCombine for Framebuffer memory. This change enables that > fix." > > [1] > https://github.com/tianocore/edk2-platforms/commit/2d0668d399708fc242336e310cc7e7bec0aec891 > [2] > https://gitlab.com/qemu-project/qemu/-/commit/24a7cd6a7c21f82f1ce9bd5ecf6fb54eb7bf4602 > [3] > https://github.com/tianocore/edk2/commit/c1d1910be6e04a8b1a73090cf2881fb698947a6e > [4] https://gitlab.com/buildroot.org/buildroot/-/jobs/7764483764 > [5] > https://gitlab.com/qemu-project/qemu/-/commit/6c84daac58f0d75a908626faf89a832fc0532140 > [6] > https://github.com/tianocore/edk2-platforms/commit/3f08401365d67e10924c774e6c3f64be56bc15b6 > > Fixes: > https://gitlab.com/buildroot.org/buildroot/-/jobs/7764483764 > > Signed-off-by: Romain Naour <romain.naour@smile.fr> > Cc: Waldemar Brodkorb <wbx@openadk.org> > --- > ...oDxe-add-feature-PCD-to-remap-frameb.patch | 129 ++++++++++++++++++ > boot/edk2/edk2.hash | 2 +- > boot/edk2/edk2.mk | 2 +- > package/edk2-platforms/edk2-platforms.hash | 2 +- > package/edk2-platforms/edk2-platforms.mk | 2 +- > 5 files changed, 133 insertions(+), 4 deletions(-) > create mode 100644 > boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > > diff --git > a/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > b/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > new file mode 100644 > index 0000000000..5f6ceb289d > --- /dev/null > +++ > b/boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > @@ -0,0 +1,129 @@ > +From 921c78f57a16b00debd58899a48e7045015c374b Mon Sep 17 00:00:00 2001 > +From: Ard Biesheuvel <ardb@kernel.org> > +Date: Mon, 17 Jun 2024 17:07:41 +0200 > +Subject: [PATCH] OvmfPkg/QemuVideoDxe: add feature PCD to remap > framebuffer > + W/C > + > +Some platforms (such as SBSA-QEMU on recent builds of the emulator) > only > +tolerate misaligned accesses to normal memory, and raise alignment > +faults on such accesses to device memory, which is the default for > PCIe > +MMIO BARs. > + > +When emulating a PCIe graphics controller, the framebuffer is > typically > +exposed via a MMIO BAR, while the disposition of the region is closer > to > +memory (no side effects on reads or writes, except for the changing > +picture on the screen; direct random access to any pixel in the > image). > + > +In order to permit the use of such controllers on platforms that only > +tolerate these types of accesses for normal memory, it is necessary to > +remap the memory. Use the DXE services to set the desired capabilities > +and attributes. > + > +Hide this behavior under a feature PCD so only platforms that really > +need it can enable it. (OVMF on x86 has no need for this) > + > +Signed-off-by: Ard Biesheuvel <ardb@kernel.org> > +Upstream: > https://github.com/tianocore/edk2/commit/c1d1910be6e04a8b1a73090cf2881fb698947a6e > +Signed-off-by: Romain Naour <romain.naour@smile.fr> On my side (this series applied on top of branch master at 81e7806), this patch does not apply. This can be reproduced with: make qemu_aarch64_sbsa_defconfig make edk2-patch Which fails with output: Applying 0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch using patch: patching file OvmfPkg/OvmfPkg.dec Hunk #1 FAILED at 444 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file OvmfPkg/OvmfPkg.dec.rej patching file OvmfPkg/QemuVideoDxe/Gop.c Hunk #1 FAILED at 9 (different line endings). Hunk #2 FAILED at 54 (different line endings). Hunk #3 FAILED at 79 (different line endings). 3 out of 3 hunks FAILED -- saving rejects to file OvmfPkg/QemuVideoDxe/Gop.c.rej patching file OvmfPkg/QemuVideoDxe/Qemu.h Hunk #1 FAILED at 13 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file OvmfPkg/QemuVideoDxe/Qemu.h.rej patching file OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf Hunk #1 FAILED at 44 (different line endings). Hunk #2 FAILED at 61 (different line endings). 2 out of 2 hunks FAILED -- saving rejects to file OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf.rej Could you have a look please? > +--- > + OvmfPkg/OvmfPkg.dec | 5 +++++ > + OvmfPkg/QemuVideoDxe/Gop.c | 19 +++++++++++++++++++ > + OvmfPkg/QemuVideoDxe/Qemu.h | 2 +- > + OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf | 4 ++++ > + 4 files changed, 29 insertions(+), 1 deletion(-) > + > +diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec > +index 51be9a5959..2c40de8a13 100644 > +--- a/OvmfPkg/OvmfPkg.dec > ++++ b/OvmfPkg/OvmfPkg.dec > +@@ -444,3 +444,8 @@ > + > + ## This feature flag indicates the firmware build supports secure > boot. > + > gUefiOvmfPkgTokenSpaceGuid.PcdSecureBootSupported|FALSE|BOOLEAN|0x6d > ++ > ++ ## Whether QemuVideoDxe should perform a EFI_MEMORY_WC remap of the > PCI > ++ # framebuffer. This might be required on platforms that do not > tolerate > ++ # misaligned accesses otherwise. > ++ > gUefiOvmfPkgTokenSpaceGuid.PcdRemapFrameBufferWriteCombine|FALSE|BOOLEAN|0x75 > +diff --git a/OvmfPkg/QemuVideoDxe/Gop.c b/OvmfPkg/QemuVideoDxe/Gop.c > +index b11eed7558..a29c025afd 100644 > +--- a/OvmfPkg/QemuVideoDxe/Gop.c > ++++ b/OvmfPkg/QemuVideoDxe/Gop.c > +@@ -9,6 +9,8 @@ > + > + #include "Qemu.h" > + > ++#include <Library/DxeServicesTableLib.h> > ++ > + STATIC > + VOID > + QemuVideoCompleteModeInfo ( > +@@ -54,6 +56,7 @@ QemuVideoCompleteModeData ( > + EFI_GRAPHICS_OUTPUT_MODE_INFORMATION *Info; > + EFI_ACPI_ADDRESS_SPACE_DESCRIPTOR *FrameBufDesc; > + QEMU_VIDEO_MODE_DATA *ModeData; > ++ EFI_STATUS Status; > + > + ModeData = &Private->ModeData[Mode->Mode]; > + Info = Mode->Info; > +@@ -79,6 +82,22 @@ QemuVideoCompleteModeData ( > + (UINT64)Mode->FrameBufferSize > + )); > + > ++ if (FeaturePcdGet (PcdRemapFrameBufferWriteCombine)) { > ++ Status = gDS->SetMemorySpaceCapabilities ( > ++ FrameBufDesc->AddrRangeMin, > ++ FrameBufDesc->AddrLen, > ++ EFI_MEMORY_UC | EFI_MEMORY_WC | EFI_MEMORY_XP > ++ ); > ++ ASSERT_EFI_ERROR (Status); > ++ > ++ Status = gDS->SetMemorySpaceAttributes ( > ++ FrameBufDesc->AddrRangeMin, > ++ FrameBufDesc->AddrLen, > ++ EFI_MEMORY_WC | EFI_MEMORY_XP > ++ ); > ++ ASSERT_EFI_ERROR (Status); > ++ } > ++ > + FreePool (FrameBufDesc); > + return EFI_SUCCESS; > + } > +diff --git a/OvmfPkg/QemuVideoDxe/Qemu.h b/OvmfPkg/QemuVideoDxe/Qemu.h > +index 57341a0bbf..a3da725fbf 100644 > +--- a/OvmfPkg/QemuVideoDxe/Qemu.h > ++++ b/OvmfPkg/QemuVideoDxe/Qemu.h > +@@ -13,7 +13,7 @@ > + #ifndef _QEMU_H_ > + #define _QEMU_H_ > + > +-#include <Uefi.h> > ++#include <PiDxe.h> > + #include <Protocol/GraphicsOutput.h> > + #include <Protocol/PciIo.h> > + #include <Protocol/DriverSupportedEfiVersion.h> > +diff --git a/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf > b/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf > +index 43a6e07faa..4c0870171b 100644 > +--- a/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf > ++++ b/OvmfPkg/QemuVideoDxe/QemuVideoDxe.inf > +@@ -44,6 +44,7 @@ > + > + [LibraryClasses] > + BaseMemoryLib > ++ DxeServicesTableLib > + FrameBufferBltLib > + DebugLib > + DevicePathLib > +@@ -61,6 +62,9 @@ > + gEfiDevicePathProtocolGuid # PROTOCOL BY_START > + gEfiPciIoProtocolGuid # PROTOCOL TO_START > + > ++[FeaturePcd] > ++ gUefiOvmfPkgTokenSpaceGuid.PcdRemapFrameBufferWriteCombine > ++ > + [Pcd] > + gUefiOvmfPkgTokenSpaceGuid.PcdOvmfHostBridgePciDevId > + gUefiOvmfPkgTokenSpaceGuid.PcdVideoResolutionSource > +-- > +2.45.0 > + > diff --git a/boot/edk2/edk2.hash b/boot/edk2/edk2.hash > index f7daa8ddf3..abcf3c6b8e 100644 > --- a/boot/edk2/edk2.hash > +++ b/boot/edk2/edk2.hash > @@ -1,3 +1,3 @@ > # Locally calculated > -sha256 > 6bdfdffcc2235a117b3f9d4124da63103f19ff30157673f812e1093b20ebb7ad > edk2-edk2-stable202308-git4.tar.gz > +sha256 > 4595b9d9d14c06bd03f575e4b7623574a4a874ef465652ecdc224099a5b14fc7 > edk2-edk2-stable202405-git4.tar.gz > sha256 > 50ce20c9cfdb0e19ee34fe0a51fc0afe961f743697b068359ab2f862b494df80 > License.txt > diff --git a/boot/edk2/edk2.mk b/boot/edk2/edk2.mk > index e5816b353a..145a9a80ae 100644 > --- a/boot/edk2/edk2.mk > +++ b/boot/edk2/edk2.mk > @@ -4,7 +4,7 @@ > # > > ################################################################################ > > -EDK2_VERSION = edk2-stable202308 > +EDK2_VERSION = edk2-stable202405 When we bumping boot/edk2, we usually also bump edk2-non-osi. See: https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/edk2-non-osi/edk2-non-osi.mk?ref_type=heads#L7 Even if it is not needed to fix the qemu_aarch64_sbsa_defconfig of this series, it would be better to keep all those components aligned. Could you check if edk2-non-osi needs to be updated too? If yes, could you update it? If no, could you add a mention that it does not need to? Maybe we could add a comment in boot/edk2/edk2.mk, before EDK2_VERSION. Something like: # When updating version, make sure to also update the edk2-platforms # and edk2-non-osi packages to their respective commit ID nearest to # the edk2 release. > EDK2_SITE = https://github.com/tianocore/edk2 > EDK2_SITE_METHOD = git > EDK2_LICENSE = BSD-2-Clause-Patent > diff --git a/package/edk2-platforms/edk2-platforms.hash > b/package/edk2-platforms/edk2-platforms.hash > index 4c74c7dfb6..0095d4298d 100644 > --- a/package/edk2-platforms/edk2-platforms.hash > +++ b/package/edk2-platforms/edk2-platforms.hash > @@ -1,3 +1,3 @@ > # Locally calculated > -sha256 > c240a8ec7816bc5963d881c84eb18d880e9269c117cfc46a3106b0c5e6e80c66 > edk2-platforms-e509ac5a729ebe2a3bc905aed1df23226aca4dc9.tar.gz > +sha256 > 41fa720ac644ec0523c576ff28eba5e0308c9649111ce42f7d408b8d8b30eaf5 > edk2-platforms-3f08401365d67e10924c774e6c3f64be56bc15b6.tar.gz > sha256 > 50ce20c9cfdb0e19ee34fe0a51fc0afe961f743697b068359ab2f862b494df80 > License.txt > diff --git a/package/edk2-platforms/edk2-platforms.mk > b/package/edk2-platforms/edk2-platforms.mk > index 7bd86ff159..23d9221649 100644 > --- a/package/edk2-platforms/edk2-platforms.mk > +++ b/package/edk2-platforms/edk2-platforms.mk > @@ -5,7 +5,7 @@ > > ################################################################################ > > # Keep in sync with latest commit as of the release date for boot/edk2 > -EDK2_PLATFORMS_VERSION = e509ac5a729ebe2a3bc905aed1df23226aca4dc9 > +EDK2_PLATFORMS_VERSION = 3f08401365d67e10924c774e6c3f64be56bc15b6 > EDK2_PLATFORMS_SITE = $(call > github,tianocore,edk2-platforms,$(EDK2_PLATFORMS_VERSION)) > EDK2_PLATFORMS_LICENSE = BSD-2-Clause-Patent > EDK2_PLATFORMS_LICENSE_FILES = License.txt > -- > 2.45.0 > > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot Best regards, Julien. _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 2024-10-28 20:27 ` Julien Olivain @ 2024-10-28 21:12 ` Thomas Petazzoni via buildroot 2024-10-29 9:56 ` Romain Naour via buildroot 0 siblings, 1 reply; 7+ messages in thread From: Thomas Petazzoni via buildroot @ 2024-10-28 21:12 UTC (permalink / raw) To: Julien Olivain; +Cc: Romain Naour, buildroot On Mon, 28 Oct 2024 21:27:30 +0100 Julien Olivain <ju.o@free.fr> wrote: > On my side (this series applied on top of branch master at 81e7806), > this patch does not apply. This can be reproduced with: > > make qemu_aarch64_sbsa_defconfig > make edk2-patch > > Which fails with output: > > Applying > 0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch using > patch: I'd say there's a fairly high chance this isn't Romain's fault. I haven't checked but I would guess that this EDK2 code base uses DOS-style new lines (\r\n), and so the patches have those, but they get stripped when going through the mailing list, making the patch unapplicable. > When we bumping boot/edk2, we usually also bump edk2-non-osi. > See: > https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/edk2-non-osi/edk2-non-osi.mk?ref_type=heads#L7 > > Even if it is not needed to fix the qemu_aarch64_sbsa_defconfig of > this series, it would be better to keep all those components aligned. > > Could you check if edk2-non-osi needs to be updated too? > If yes, could you update it? > If no, could you add a mention that it does not need to? > > Maybe we could add a comment in boot/edk2/edk2.mk, before EDK2_VERSION. > Something like: > > # When updating version, make sure to also update the edk2-platforms > # and edk2-non-osi packages to their respective commit ID nearest to > # the edk2 release. I'll let Romain address this point before applying then. Thanks! Thomas -- Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 2024-10-28 21:12 ` Thomas Petazzoni via buildroot @ 2024-10-29 9:56 ` Romain Naour via buildroot 2024-10-29 20:51 ` Julien Olivain 0 siblings, 1 reply; 7+ messages in thread From: Romain Naour via buildroot @ 2024-10-29 9:56 UTC (permalink / raw) To: Thomas Petazzoni, Julien Olivain; +Cc: buildroot Hello Julien, Thomas, Le 28/10/2024 à 22:12, Thomas Petazzoni a écrit : > On Mon, 28 Oct 2024 21:27:30 +0100 > Julien Olivain <ju.o@free.fr> wrote: > >> On my side (this series applied on top of branch master at 81e7806), >> this patch does not apply. This can be reproduced with: >> >> make qemu_aarch64_sbsa_defconfig >> make edk2-patch >> >> Which fails with output: >> >> Applying >> 0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch using >> patch: > > I'd say there's a fairly high chance this isn't Romain's fault. I > haven't checked but I would guess that this EDK2 code base uses > DOS-style new lines (\r\n), and so the patches have those, but they get > stripped when going through the mailing list, making the patch > unapplicable. Indeed, this is our well known issue with the mailing list [The correct patch file] $ file boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch: unified diff output, ASCII text, with CRLF, LF line terminators [The corrupted patch file] $ file boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch: unified diff output, ASCII text > >> When we bumping boot/edk2, we usually also bump edk2-non-osi. >> See: >> https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/edk2-non-osi/edk2-non-osi.mk?ref_type=heads#L7 >> >> Even if it is not needed to fix the qemu_aarch64_sbsa_defconfig of >> this series, it would be better to keep all those components aligned. >> >> Could you check if edk2-non-osi needs to be updated too? >> If yes, could you update it? >> If no, could you add a mention that it does not need to? >> >> Maybe we could add a comment in boot/edk2/edk2.mk, before EDK2_VERSION. >> Something like: >> >> # When updating version, make sure to also update the edk2-platforms >> # and edk2-non-osi packages to their respective commit ID nearest to >> # the edk2 release. > > I'll let Romain address this point before applying then. There is no information from edk2 releases about edk2-non-osi and edk2-platforms git hashes to use. At least Qemu testsuite files contains the hash used for their tests [1]... Actually I'm not sure if edk2-non-osi package is really needed since it contains mostly prebuilt firmwares. meta-arm doesn't use it: https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-bsp/uefi/edk2-firmware.inc?h=scarthgap#n18 Actually this package is only needed for Marvell Armada [2] (Silicon/Marvell/Armada7k8k/DeviceTree) that was not updated since 2021 in edk2-non-osi repository. So, no update is required. [1] https://gitlab.com/qemu-project/qemu/-/commit/24a7cd6a7c21f82f1ce9bd5ecf6fb54eb7bf4602 [2] https://gitlab.com/buildroot.org/buildroot/-/commit/95f72fb61aae6a64ea822b535cf9d2c2e01e6fc9 Best regards, Romain > > Thanks! > > Thomas _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 2024-10-29 9:56 ` Romain Naour via buildroot @ 2024-10-29 20:51 ` Julien Olivain 0 siblings, 0 replies; 7+ messages in thread From: Julien Olivain @ 2024-10-29 20:51 UTC (permalink / raw) To: Romain Naour; +Cc: Thomas Petazzoni, buildroot Hi Romain, Thomas, On 29/10/2024 10:56, Romain Naour wrote: > Hello Julien, Thomas, > > Le 28/10/2024 à 22:12, Thomas Petazzoni a écrit : >> On Mon, 28 Oct 2024 21:27:30 +0100 >> Julien Olivain <ju.o@free.fr> wrote: >> >>> On my side (this series applied on top of branch master at 81e7806), >>> this patch does not apply. This can be reproduced with: >>> >>> make qemu_aarch64_sbsa_defconfig >>> make edk2-patch >>> >>> Which fails with output: >>> >>> Applying >>> 0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch using >>> patch: >> >> I'd say there's a fairly high chance this isn't Romain's fault. I >> haven't checked but I would guess that this EDK2 code base uses >> DOS-style new lines (\r\n), and so the patches have those, but they >> get >> stripped when going through the mailing list, making the patch >> unapplicable. > > Indeed, this is our well known issue with the mailing list > > [The correct patch file] > $ file > boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch: > unified diff output, ASCII text, with CRLF, LF line terminators > > [The corrupted patch file] > $ file > boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch > boot/edk2/0001-OvmfPkg-QemuVideoDxe-add-feature-PCD-to-remap-frameb.patch: > unified diff output, ASCII text > I confirm the CR-LR newlines of the original patch got lost on the mailing list. If I download the patch from: https://github.com/tianocore/edk2/commit/c1d1910be6e04a8b1a73090cf2881fb698947a6e.patch It applies and build correctly. However, while testing this series a bit more, this edk2 bump breaks several runtime tests. So far, I spotted test_edk2, test_fwts and test_grub. Those tests are failing disregarding the qemu version used. When updating ATF to 2.11 in those tests, they get fixed with a recent qemu version (I tested 9.1.1), but they are still crashing in the qemu 5.2.0 in the Buildroot Docker image. This fit to your commit logs. When crashing, the output is: NOTICE: BL31: v2.11.0(release):v2.11 NOTICE: BL31: Built : 17:52:08, Oct 29 2024 UEFI firmware (version 1.0 built at 17:52:34 on Oct 29 2024) Synchronous Exception at 0x000001001F3AE0AC My guess is that we've reached the limit of this old Qemu version... I think those tests relying on recent qemu should build their own host-qemu and the runtime test infra should use it. Other tests should remain as they are. If I recall correctly, it is not the first time we get toward this conclusion... If we decide to do so, this series will need to be expanded a bit to fix those tests at the same time. I'll continue to testing on my side to see how we can improve that. >> >>> When we bumping boot/edk2, we usually also bump edk2-non-osi. >>> See: >>> https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/edk2-non-osi/edk2-non-osi.mk?ref_type=heads#L7 >>> >>> Even if it is not needed to fix the qemu_aarch64_sbsa_defconfig of >>> this series, it would be better to keep all those components aligned. >>> >>> Could you check if edk2-non-osi needs to be updated too? >>> If yes, could you update it? >>> If no, could you add a mention that it does not need to? >>> >>> Maybe we could add a comment in boot/edk2/edk2.mk, before >>> EDK2_VERSION. >>> Something like: >>> >>> # When updating version, make sure to also update the edk2-platforms >>> # and edk2-non-osi packages to their respective commit ID nearest to >>> # the edk2 release. >> >> I'll let Romain address this point before applying then. > > There is no information from edk2 releases about edk2-non-osi and > edk2-platforms > git hashes to use. At least Qemu testsuite files contains the hash used > for > their tests [1]... > > Actually I'm not sure if edk2-non-osi package is really needed since it > contains > mostly prebuilt firmwares. > > meta-arm doesn't use it: > > https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-bsp/uefi/edk2-firmware.inc?h=scarthgap#n18 > > Actually this package is only needed for Marvell Armada [2] > (Silicon/Marvell/Armada7k8k/DeviceTree) that was not updated since 2021 > in > edk2-non-osi repository. > > So, no update is required. Ok, thanks for this confirmation. > [1] > https://gitlab.com/qemu-project/qemu/-/commit/24a7cd6a7c21f82f1ce9bd5ecf6fb54eb7bf4602 > [2] > https://gitlab.com/buildroot.org/buildroot/-/commit/95f72fb61aae6a64ea822b535cf9d2c2e01e6fc9 > > Best regards, > Romain > > >> >> Thanks! >> >> Thomas Best regards, Julien. _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] [PATCH v2 3/3] configs/qemu_aarch64_sbsa_defconfig: switch to neoverse-n1 (armv8.2a) 2024-10-27 19:43 [Buildroot] [PATCH v2 1/3] configs/qemu_aarch64_sbsa_defconfig: update ATF to v2.11 Romain Naour via buildroot 2024-10-27 19:43 ` [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 Romain Naour via buildroot @ 2024-10-27 19:43 ` Romain Naour via buildroot 1 sibling, 0 replies; 7+ messages in thread From: Romain Naour via buildroot @ 2024-10-27 19:43 UTC (permalink / raw) To: buildroot; +Cc: Romain Naour The SBSA Reference Platform was updated to neoverse-n1 (armv8.2a) in Qemu v8.1 [1]. BR2_cortex_a57: # cat /proc/cpuinfo processor : 0 BogoMIPS : 2000.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x1 CPU part : 0xd07 CPU revision : 0 [...] BR2_neoverse_n1: # cat /proc/cpuinfo processor : 0 BogoMIPS : 2000.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x4 CPU part : 0xd0c CPU revision : 1 [...] Tests test_fwts.py test_edk2.py using BR2_TARGET_EDK2_PLATFORM_QEMU_SBSA=y are not updated to neoverse-n1 since the Qemu used by the gitlab-ci is too old (5.2.0 while 8.1 is required). Note: SBSA Reference Platform was recently updated again to neoverse-n2 (armv9.0a) in Qemu v9.1 [2]. But there is no armv9.0a support yet in Buildroot. [1] https://gitlab.com/qemu-project/qemu/-/commit/1877272bad7b08b67312503ee66184279876c7bd [2] https://gitlab.com/qemu-project/qemu/-/commit/b1d592e7b0a7301eae8e3baa99744ac35db3cd2a Signed-off-by: Romain Naour <romain.naour@smile.fr> --- v2: update a typo in the commit log (neoverse-n1/neoverse-n2) --- board/qemu/aarch64-sbsa/readme.txt | 2 +- configs/qemu_aarch64_sbsa_defconfig | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/board/qemu/aarch64-sbsa/readme.txt b/board/qemu/aarch64-sbsa/readme.txt index cf5f66d4d6..7d97d7f6ab 100644 --- a/board/qemu/aarch64-sbsa/readme.txt +++ b/board/qemu/aarch64-sbsa/readme.txt @@ -17,7 +17,7 @@ Run the emulation with: qemu-system-aarch64 \ -M sbsa-ref \ - -cpu cortex-a57 \ + -cpu neoverse-n1 \ -smp 4 \ -m 1024 \ -nographic \ diff --git a/configs/qemu_aarch64_sbsa_defconfig b/configs/qemu_aarch64_sbsa_defconfig index 23d274b529..6df2b2e273 100644 --- a/configs/qemu_aarch64_sbsa_defconfig +++ b/configs/qemu_aarch64_sbsa_defconfig @@ -1,5 +1,5 @@ BR2_aarch64=y -BR2_cortex_a57=y +BR2_neoverse_n1=y BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6=y BR2_GLOBAL_PATCH_DIR="board/qemu/patches" BR2_DOWNLOAD_FORCE_CHECK_HASHES=y -- 2.45.0 _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply related [flat|nested] 7+ messages in thread
end of thread, other threads:[~2024-10-29 20:52 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2024-10-27 19:43 [Buildroot] [PATCH v2 1/3] configs/qemu_aarch64_sbsa_defconfig: update ATF to v2.11 Romain Naour via buildroot 2024-10-27 19:43 ` [Buildroot] [PATCH v2 2/3] boot/edk2: bump to version edk2-stable202405 Romain Naour via buildroot 2024-10-28 20:27 ` Julien Olivain 2024-10-28 21:12 ` Thomas Petazzoni via buildroot 2024-10-29 9:56 ` Romain Naour via buildroot 2024-10-29 20:51 ` Julien Olivain 2024-10-27 19:43 ` [Buildroot] [PATCH v2 3/3] configs/qemu_aarch64_sbsa_defconfig: switch to neoverse-n1 (armv8.2a) Romain Naour via buildroot
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.