| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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'
|
| |
|
|
|
|
|
|
|
|
| |
Options updated (with new values):
CONFIG_COMPRESS_RAMSTAGE=y
CONFIG_VBOOT_FWID_VERSION="$(KERNELVERSION)"
CONFIG_GBB_FLAG_ENABLE_ALTERNATE_OS=y
CONFIG_GBB_FLAG_FORCE_DEV_SWITCH_ON=y
|
|
|
|
|
| |
Config updated using 'olddefconfig' make target with revision
located at "projects/coreboot/configs/revision"
|
|
|
|
|
|
|
| |
Options updated (with new values):
CONFIG_COMPRESS_RAMSTAGE=y
CONFIG_VBOOT_FWID_VERSION="$(KERNELVERSION)"
# CONFIG_GBB_FLAG_DISABLE_EC_SOFTWARE_SYNC is not set
|
|
|
|
|
| |
Config updated using 'olddefconfig' make target with revision
located at "projects/coreboot/configs/revision"
|
|
|
|
|
|
|
|
| |
Options updated (with new values):
CONFIG_COMPRESS_RAMSTAGE=y
CONFIG_VBOOT_FWID_VERSION="$(KERNELVERSION)"
CONFIG_GBB_FLAG_ENABLE_ALTERNATE_OS=y
CONFIG_GBB_FLAG_FORCE_DEV_SWITCH_ON=y
|
|
|
|
|
| |
Config updated using 'olddefconfig' make target with revision
located at "projects/coreboot/configs/revision"
|
|
|
|
|
|
|
|
| |
Options updated (with new values):
CONFIG_COMPRESS_RAMSTAGE=y
CONFIG_VBOOT_FWID_VERSION="$(KERNELVERSION)"
CONFIG_GBB_FLAG_ENABLE_ALTERNATE_OS=y
CONFIG_GBB_FLAG_FORCE_DEV_SWITCH_ON=y
|
|
|
|
|
| |
Config updated using 'olddefconfig' make target with revision
located at "projects/coreboot/configs/revision"
|
|
Moving the board-specific directories into projects/coreboot/configs/
and removing the payload-specific directories (depthcharge, seabios)
will allow for better management of Coreboot configs for each
board. Instead of having a config for each payload, there will be
at most two main configs (textmode, corebootfb) for each board.
Selecting a default payload will be reimplemented in a subsequent
commit.
|