| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
D945GCLF ROMs can now be built with either SeaBIOS or GRUB as
a default payload for use with a 1MiB flash, e.g.:
'./libreboot build coreboot d945gclf textmode 1mb seabios'
|
|
|
|
|
|
|
|
|
| |
Previously it was thought that only boards with 512KiB flash chips
were produced but JohnMH (in #libreboot) ran across one with an
SST25LF080A 1MiB flash.
D945GCLF Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot d945gclf textmode 1mb'
|
|
|
|
|
| |
Paul Kocialkowski was not retained as the original author due
to the triviality of the patch.
|
|
|
|
|
|
|
| |
The revision currently used has an issue building crossgcc due to
a libelf bug. Upstream no longer depends on libelf when building
crossgcc (since afda56e1ad8719a1) so using a more recent revision
sidesteps this issue.
|
| |
|
|
|
|
|
|
|
| |
Z61t ROMs can now be built with either SeaBIOS or GRUB as
a default payload, e.g.:
'./libreboot build coreboot z61t textmode 2mb seabios'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2MiB flash is the default for this board. A 16MiB config is
included for those looking to modify their board with a larger flash
chip.
Also, text mode is the only display mode available for this board;
as such, inclusion of the textmode subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Z61t Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot z61t textmode 2mb'
|
| |
|
| |
|
|
|
|
|
|
|
| |
Veyron Speedy ROMs are built with Depthcharge as the default payload,
e.g.:
'./libreboot build coreboot veyron speedy corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is included
for those looking to modify their board with a larger flash chip.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Veyron Speedy Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot veyron speedy corebootfb 4mb'
|
| |
|
|
|
|
|
|
|
| |
Veyron Minnie ROMs are built with Depthcharge as the default payload,
e.g.:
'./libreboot build coreboot veyron minnie corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is included
for those looking to modify their board with a larger flash chip.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Veyron Minnie Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot veyron minnie corebootfb 4mb'
|
| |
|
|
|
|
|
|
|
| |
Veyron Mickey ROMs are built with Depthcharge as the default payload,
e.g.:
'./libreboot build coreboot veyron mickey corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is not
included (yet) as I was unable to find a teardown of this device
(Asus Chromebit CS10) online to be sure that reassembly is possible.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Veyron Mickey Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot veyron mickey corebootfb 4mb'
|
|
|
|
|
|
|
| |
Veyron Jerry ROMs are built with Depthcharge as the default payload,
e.g.:
'./libreboot build coreboot veyron jerry corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is
included for those looking to modify their board with a larger flash
chip.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Veyron Jerry Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot veyron jerry corebootfb 4mb'
|
| |
|
|
|
|
|
|
|
| |
Nyan Blaze ROMs are built with Depthcharge as the default payload,
e.g.:
'./libreboot build coreboot nyan blaze corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is
included for those looking to modify their board with a larger flash
chip.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Nyan Blaze Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot nyan blaze corebootfb 4mb'
|
|
|
|
|
|
| |
Nyan Big ROMs are built with Depthcharge as its default payload, e.g.:
'./libreboot build coreboot nyan big corebootfb 4mb depthcharge'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4MiB flash is the default for this board. A 16MiB config is
included for those looking to modify their board with a larger flash
chip.
Also, corebootfb is the only display mode available for this board;
as such, inclusion of the corebootfb subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Nyan Big Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot nyan big corebootfb 4mb'
|