Dear Carl-Daniel and coreboot folks,
to attract new developers from my (inexperienced) point of view possible contributors hesitate because they think doing coreboot development will be searching for and reading a lot of data sheets, do reverse engineering, bricking boards, etc.. So to attract contributors one could point out that there are more or less hardware unrelated tasks to do and that interested people also can do (easy) hardware related stuff and learn things by looking at the infrastructure projects Patrick listed at [1]. Additionally more “conventional” (software) programming is needed to get more payloads (configuration payload to for example set up RAM timing), create images that fit in a flash chip (for recovery maybe) and (graphical) configuration tools for example for `nvramtool`. But not knowing for sure the reasons people stay away from coreboot development this is of course just a suggestion and a guess. Thanks, Paul [1] http://www.coreboot.org/Infrastructure_Projects
signature.asc
Description: This is a digitally signed message part
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
