Difference between revisions of "Easy projects"

From coreboot
Jump to navigation Jump to search
Line 24: Line 24:

* http://www.czechcomputer.cz/cat_tree.jsp?bpath=Z%C3%A1kladn%C3%AD+desky\Socket+AM2%2B\AMD+740G
* http://www.czechcomputer.cz/cat_tree.jsp?bpath=Z%C3%A1kladn%C3%AD+desky\Socket+AM2%2B\AMD+740G
=== Use CBFS wherever possible ===
* <code>src/cpu/amd/model_lx/vsmsetup.c</code> is a very good candidate. The VSM blobs should be loaded from [[CBFS]]. See [http://review.coreboot.org/gitweb?p=coreboot.git;a=commitdiff;h=9839cbd53fdcfcee52c406d9f52af924192e618d commit 9839cbd53fdcfcee52c406d9f52af924192e618d] for the new location of the code.

=== Formatting and whitespace cleanup ===
=== Formatting and whitespace cleanup ===

Revision as of 21:25, 15 April 2013

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.


AMD 740G information gathering

(This project description is not finished yet)

If you have a board with AMD 740G chipset, please run (as root)

$ flashrom -V
$ lspci -nnvvvxxxx
$ superiotool -deV
$ dmidecode

and mail the output to the coreboot mailing list together with the exact model number/name of your board.

This helps us evaluate which boards are good targets for coreboot.

Here are some boards:

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.

Ideally a check/test should be integrated into the build system pointing out these issues already when committing or testing the commit. Such tests probably already exist in other projects and just need to be copied.


coreboot can use a number of different payloads.

Add/test new supported payloads

  • Test syslinux (probably requires SeaBIOS in addition, needs to be checked).
  • Port GPXE to "native" coreboot (it works fine together with SeaBIOS though).


The flashrom tool can read/write coreboot/BIOS images from/to flash chips.