mirror of
https://git.busybox.net/buildroot.git
synced 2024-11-26 15:03:27 +08:00
cc0823c2d1
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." As a side note, the edk2-non-osi package does not need to be updated, so it is left untouched. Finally, this EDK2 version requires a recent Qemu version. The version included in the reference Docker image (5.2.0) is too old and will not allow to start this EDK2 version. Therefore, this bump is known to be incompatible with runtime tests which are using EDK2 on Aarch64 architecture. At the authoring time of this commit, broken tests are: - tests.boot.test_edk2 - tests.boot.test_grub.TestGrubAArch64EFI - tests.package.test_fwts Note that the EDK2/Qemu incompatibility is only affecting Aarch64 tests. Other tests using EDK2 on i386 or x86_64 are not affected. To prevent this commit introducing broken runtime tests, those have been disabled in a previous commit. [1] |
||
|---|---|---|
| .github | ||
| .gitlab/issue_templates | ||
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .b4-config | ||
| .checkpackageignore | ||
| .clang-format | ||
| .defconfig | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches