[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linuxbios
Subject:    [coreboot] Re: Systems that use coreboot
From:       Tim Wawrzynczak via coreboot <coreboot () coreboot ! org>
Date:       2022-05-06 14:55:07
Message-ID: CAGVHcdoTo7ENjf83dK_Tis9QqxNMZ6nW_CWmDbCWSNyHZCHmoA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, May 6, 2022 at 6:16 AM Peter Stuge <peter@stuge.se> wrote:

> 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
>

[Attachment #5 (text/html)]

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



_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org


[prev in list] [next in list] [prev in thread] [next in thread]