Valerii Gugnin wrote:
> What are the most popular systems on which coreboot is typically used?
I guess that's the various Chromebooks, all of which ship with coreboot.
> What mainboards, southbridges, SoCs etc do these systems use?
Chromebook (and related) reference mainboards live under mainboard/google/
in the codebase, but note that those are just that, reference designs.
Just a note that this is not actually the case, the OEM variant firmware is always (at least
in recent memory) able to be built as well, (see the mainboard/google/*/variants subdirectories).
Yes it does include the reference design, sometimes as a "baseboard", where the variants simply
provide their differences from the baseboard.
From these reference designs OEMs that you may already know
(Lenovo, HP, etc.) then create products which may (or may not!) have
a subdirectory of their own under mainboard/lenovo/.
Then please refer to the source code for the components used, since
that's a long list. Look at the Kconfig file (it's just a text file)
in the subdirectory for a mainboard and you'll see which different
components that board uses, in select SOUTHBRIDGE_.. etc. lines.
> What is the most used part of code (for which system) in coreboot?
A core design principle of coreboot is to maximize code reuse across
as many systems as possible. This is in contrast to common practice
among commercial IBVs where a single full codebase per mainboard is
not uncommon.
So I'd like to answer this your question with "almost everything for
all systems" but in reality some code is central and other is not.
Code in {console,device,lib}/ is explicitly generic so that should
have the largest coverage.
//Peter
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org