Documentation: Remove qemu aarch64 from project ideas

This has been implemented last year.

Change-Id: I24e40a7a9a9d7238b8c9d34656d5b62a26b8252b
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/38533
Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>

1 files changed, 0 insertions, 22 deletions

diff --git a/Documentation/contributing/project_ideas.md b/Documentation/contributing/project_ideas.md
index 5bc4cacea5..90164a2bfa 100644
--- a/Documentation/contributing/project_ideas.md
+++ b/Documentation/contributing/project_ideas.md
@@ -64,28 +64,6 @@ across architectures.
 ### Mentors
 * Timothy Pearson <tpearson@raptorengineering.com>
 
-## Support QEMU AArch64
-Having QEMU support for the architectures coreboot can boot helps with
-some (limited) compatibility testing: While QEMU generally doesn't need
-much hardware init, any CPU state changes in the boot flow will likely
-be quite close to reality.
-
-That could be used as a baseline to ensure that changes to architecture
-code doesn't entirely break these architectures
-
-### Requirements
-* coreboot knowledge: Should know the general boot flow in coreboot.
-* other knowledge: This will require knowing how the architecture
-  typically boots, to adapt the coreboot payload interface to be
-  appropriate and, for example, provide a device tree in the platform's
-  typical format.
-* hardware requirements: since QEMU runs practically everywhere and
-  needs no recovery mechanism, these are suitable projects when no special
-  hardware is available.
-
-### Mentors
-* Patrick Georgi <patrick@georgi.software>
-
 ## Add Kernel Address Sanitizer functionality to coreboot
 The Kernel Address Sanitizer (KASAN) is a runtime dynamic memory error detector.
 The idea is to check every memory access (variables) for its validity