From 3ce88e1fa0f4470b75bfa31a33fee45fa6333321 Mon Sep 17 00:00:00 2001 From: Patrick Georgi Date: Thu, 14 Feb 2019 13:24:44 +0100 Subject: Documentation: Add broader payload coverage to project ideas A couple people discussed recently how it's a shame that on some architectures we can bring up a device but then have nothing to do with it afterwards. Having payloads to choose from would help a lot there. Change-Id: Ia66f22947d09afe3076cc2ee12f5b652fe80fc3a Signed-off-by: Patrick Georgi Reviewed-on: https://review.coreboot.org/c/31415 Tested-by: build bot (Jenkins) Reviewed-by: Arthur Heymans Reviewed-by: Angel Pons --- Documentation/contributing/project_ideas.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'Documentation') diff --git a/Documentation/contributing/project_ideas.md b/Documentation/contributing/project_ideas.md index 1c23cc6bc7..2e43871149 100644 --- a/Documentation/contributing/project_ideas.md +++ b/Documentation/contributing/project_ideas.md @@ -91,3 +91,22 @@ would help to ensure code quality and make the runtime code more robust. ### Mentors * Werner Zeh + +## Port payloads to ARM, AArch64, MIPS or RISC-V +While we have a rather big set of payloads for x86 based platforms, all other +architectures are rather limited. Improve the situation by porting a payload +to one of the platforms, for example GRUB2, U-Boot (the UI part), Tianocore, +yabits, FILO, or Linux-as-Payload. + +Since this is a bit of a catch-all idea, an application to GSoC should pick a +combination of payload and architecture to support. + +### Requirements +* coreboot knowledge: Should know the general boot flow in coreboot +* other knowledge: It helps to be familiar with the architecture you want to + work on. +* hardware requirements: Much of this can be done in QEMU or other emulators, + but the ability to test on real hardware is a plus. + +### Mentors +* Simon Glass for U-Boot payload projects -- cgit v1.2.3