[coreboot] How the file, c_start.d is made?

ali hagigat hagigatali at gmail.com
Wed Oct 27 13:43:21 CEST 2010

Thank you Peter to advice me to study the Coreboot source code and
learn new things (my ultimate purpose is the same dear) but simple
question is this:

Where is the first lines of Coreboot to study? Where do I have to look
at in the beginning to understand the algorithm of Coreboot? What will
be the code/data flow?

Answering to these questions make me return back to the build process
to know the logical relationship of the source code fragments and
another thing is how and where the source code functions and fragments
have been written(I mean what physical addresses)?

You say something but it can not be done in practice dear...

How you are a Coreboot expert while you do not know even what will
make c_start.d? When you start studying the files which will be built
for Coreboot you will face with this dragon very soon.

Sometimes a person wants to change a specific part of a source code
and he has a professional manager, while his manager masters the code
perfectly but he needs new changes and hires an engineer and take him
over some responsibilities. This is one story, but another scenario is
when a person is completely stranger to the code and must understand
the whole project by himself.

He must deal with any thing related to the project from build to the
internal code, every thing.

Best Regards

On Tue, Oct 26, 2010 at 1:51 PM, Peter Stuge <peter at stuge.se> wrote:
> ali hagigat wrote:
>> what rule is making the file, c_start.d itself?
> It's very strange that you are so obsessed with the build system so
> many months after starting to look at coreboot.
> I first looked at coreboot nearly 10 years ago, and while I am not
> super active in the codebase there are still *so* many other *actual*
> things to work on and learn about *in the code*.
> You've mentioned that you want to study coreboot before you can work
> with it, but I would recommend that you stop studying the build
> system for now and look more at what coreboot *code* is actually
> doing. This is especially true if you are not already very skilled
> with the GNU toolchain and make, because building coreboot can
> sometimes require special tricks.
> To also answer your question, I suggest that you study the output
> from
> make V=1
> and see which command creates the c_start.d file. Then you could
> probably locate it within the Makefiles.
> //Peter
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot

More information about the coreboot mailing list