| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ |
|
| | |
| | |
| | |
| | | |
Output is fixed with a5babe37f42cc162812f8ed3310a1e0c45eabb67
|
| | |
| | |
| | |
| | | |
Makes it easier to read when multiple terse actions are performed.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Avoid redundant actions if certain projects which are part of
another (e.g. crossgcc in the coreboot repository) are left out of the
download process.
|
|\ \ \ |
|
|/ / / |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
There is more than one correct ordering of projects in this file;
"correct" includes handling of project dependencies.
|
| |/ /
| | |
| | |
| | |
| | | |
Projects listed in this file are those (and their dependencies)
which are necessary for creating Libreboot images in all configurations.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
The projects listed in this file are those which are built when
running the build action.
|
|/ /
| |
| |
| |
| | |
All tools currently in the build system should be represented
in these files now.
|
|\ \
| |/
|/| |
|
|/
|
|
|
| |
Turns out people mislabel them, most likely candidate for those boards are
Wistron RP-1/RP-4 in several variants. See #589
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\ |
|
|/ |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Projects listed in projects/coreboot/configs/dependencies
are the minimum required by all boards.
Dependencies required by a target in addition to those
specified in parent dependencies files may be declared in the target's
directory, e.g:
projects/coreboot/configs/x200/dependencies
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Projects may now declare other projects it depends upon through
the file "dependencies" located in a project's $CONFIGS directory.
This file requires that each dependency listed, one per line,
correspond to a project in the $PROJECTS directory; the dependency
may be in any form accepted by the libreboot script, e.g:
./libreboot build $dependency
Multiple dependencies files, one per target, are read provided
they are located in target directories and those targets were
included in the list of arguments passed to the libreboot script.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The intent is to create a simple rule of thumb where arguments
are given beginning with those that relate to the device's physical
attributes, such as flash chip size, continuing with arguments
on how to use the hardware (e.g. display mode), and ending with
anything else.
|