Easy projects: Difference between revisions
PaulePanter (talk | contribs) m (Fix syntax of section formatting so »Formatting and whitespace cleanup« is formatted correctly.) |
|||
Line 30: | Line 30: | ||
=== Formatting and whitespace cleanup == | === 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 requires 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 requires review. |
Revision as of 09:20, 28 March 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.
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 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:
Use CBFS wherever possible
- src/cpu/amd/model_lx/vsmsetup.c is a very good candidate. The VSM blobs should be loaded from CBFS.
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 requires review.
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).
- Port GPXE to "native" coreboot (it works fine together with SeaBIOS though).
flashrom
The flashrom tool can read/write coreboot/BIOS images from/to flash chips.
- See flashrom's Easy Projects list for details.