Infrastructure Projects

From coreboot
Revision as of 23:40, 23 June 2009 by Uwe (talk | contribs) (→‎More ideas: Common payload location.)
Jump to navigation Jump to search

The wiki is being retired!

Documentation is now handled by the same processes we use for code: Add something to the Documentation/ directory in the coreboot repo, and it will be rendered to Contributions welcome!

This page collects a list of projects to improve the infrastructure of coreboot-v2. Infrastructure means those parts of the code that aren't chipset or mainboard specific, but are used by all of them.

The idea is to consolidate a list of things "to do" with their status and responsible developers.

In progress


A filesystem-alike layout for the coreboot image, to enable systems like bayou and to clean up the system in general (eg. no more buildrom)


Upstream, implemented on some boards. Known problems on some boards.


Stefan, Ron, Patrick, Myles

Low/High Tables

SeaBIOS requires a copy of various BIOS tables outside the fseg as it overwrites that segment. Generally clean out the table generation code.


Upstream, implemented on some boards. Problems on others.



Port v3 Resource Allocator

The v3 resource allocator should be ported to v2


Patches exist.



More ideas


There is some locking infrastructure in printk_*, but there are many copies of that code, with their own locking or none at all. Unification of that would fix hard to decipherable garbage on serial.

Unify ACPI

Every ACPI board has its own routines to compile the ACPI sources. Unify that. Also, figure out generic ACPI code and deduplicate it

Build System

The current system of generated Makefiles is non-ideal (for too many reasons for this little margin). Fix it, somehow

Config System

Use KConfig (or something else) that improves on the current situation.

Unify fallback/normal switch

Right now, the decision whether to use fallback or normal is in cache_as_ram_auto.c in many boards. Make that generic again (also helps with further CBFSification at some point).

Common payload location

Many boards in v2 have different names for the payload in targets/.../ (payload.elf, filo.elf, etherboot.elf, etc) and locations (../payload.elf, or various absolute paths which only work for one developer). We should fix this by using ../payload.elf as common payload name/location for all boards. A long-term solution will probably be the use of Kconfig in v2 where the user specifies a payload manually as in v3.