Difference between revisions of "Easy projects"

From coreboot
Jump to: navigation, search
(Use CBFS wherever possible: Add link to commit changing the location for referenced code.)
 
(3 intermediate revisions by 3 users not shown)
Line 4: Line 4:
  
 
== coreboot ==
 
== coreboot ==
 
 
=== 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 [[Mailinglist|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:
 
 
* 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 ===
Line 33: Line 9:
 
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.
 
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.
+
=== 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.
  
 
== Payloads ==
 
== Payloads ==
Line 42: Line 20:
  
 
* Test syslinux (probably requires [[SeaBIOS]] in addition, needs to be checked).
 
* Test syslinux (probably requires [[SeaBIOS]] in addition, needs to be checked).
* Port [[GPXE]] to "native" coreboot (it works fine together with [[SeaBIOS]] though).
 
  
 
== flashrom ==
 
== flashrom ==
  
The [[flashrom]] tool can read/write coreboot/BIOS images from/to flash chips.
+
The [http://www.flashrom.org flashrom] tool can read/write coreboot/BIOS images from/to flash chips.
  
 
* See [http://flashrom.org/Easy_projects flashrom's Easy Projects] list for details.
 
* See [http://flashrom.org/Easy_projects flashrom's Easy Projects] list for details.

Latest revision as of 15:16, 17 March 2016

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.

coreboot

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.

Payloads

coreboot can use a number of different payloads.

Add/test new supported payloads

  • Test syslinux (probably requires SeaBIOS in addition, needs to be checked).

flashrom

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

Other