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 https://doc.coreboot.org/. Contributions welcome!
You probably came here trying to find a small (minutes to hours) and easy task where you can get your hands dirty and get results immediately.
If you're a coreboot or flashrom newbie, this page is for you.
Formatting and whitespace cleanup
We try to maintain the code in the Development_Guidelines#Coding_Style Linux style, but occasionally white-space and other formatting issues find their way into the project. Formatting and white-space changes should be done in small groups as a separate patch from code changes. Be careful running indent/lindent. The results are not always the right thing to do and require review.
Adding copyright headers to all files
We want to have copyright headers on all .c, .h, and .asl files (and maybe others as well, but if we had them in all of these files, that would be great.) The list of files that don't have headers can be seen by running the util/lint/lint-000-license-headers script from the coreboot directory. To add a header to the file, you need to verify the origin of the file, so you should run a git log on it. There may also already be information at the top of the file about what kind of license should be used. If the file is original to coreboot, it should get the standard coreboot license header. If it has some other license, the appropriate header should be added.
coreboot can use a number of different payloads.
Add/test new supported payloads
- Test syslinux (probably requires SeaBIOS in addition, needs to be checked).
The flashrom tool can read/write coreboot/BIOS images from/to flash chips.
- See flashrom's Easy Projects list for details.