so is your plan to port the UEFI code as a payload or to use u-boot as a payload and then use their UEFI support?
On Sat, Mar 12, 2022 at 9:36 AM Ahamed Husni ahamedhusni73@gmail.com wrote:
Hi everyone,
On Fri, Feb 25, 2022 at 4:21 PM Ahamed Husni ahamedhusni73@gmail.com wrote:
Dear All,
I am hoping to apply for the GSoC 2022 program. I am really interested in contributing to the coreboot project as I love to work with low level development.
I completed the pre-requisites mentioned in the documentation.
I built a 32-bit EFI binary in the gnu-efi environment. I used U-Boot as the payload for coreboot to test this EFI binary. The target is x86_64(QEMU). Serial output: https://gist.github.com/drac98/6166d29f6c3a2baf2f4e791925ea98d3
I sent a patch for review about a year ago related to adding heap-out-of-bound detection support to AddressSanitizer port. If this is not acceptable as my first patch for review, please let me know. I can fix some coding styles or do a simple task given by the community. PATCH: https://review.coreboot.org/c/coreboot/+/51787
I find the "Add U-BOOT's UEFI payload as a coreboot payload" project mentioned in the coreboot project collection interesting to me. I have no prior experience with UEFI. As a starting point I learned to build and run an EFI binary with coreboot using the U-Boot payload.
Please let me know what I should do next to learn and prepare for this project.
Thanks & Best regards, Husni.
I reached out to the U-Boot community to check the current status of the UEFI. Please find the thread here: https://lists.denx.de/pipermail/u-boot/2022-March/477682.html
I have a few questions about the project. What should be the deliverables for this project? Do we need 64-bit EFI support (U-Boot doesn't support 64bit EFI)? How do we develop a payload? Is it done using libpayload? Is this a medium sized project or a large project?
--Husni