| 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.
|
| | |
|
| |
|
|
|
|
|
| |
D510MO ROMs can now be built with either SeaBIOS or GRUB as
a default payload, e.g.:
'./libreboot build coreboot d510mo textmode 1mb seabios'
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
1MiB 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.
D510MO Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot d510mo textmode 1mb'
|
|
|
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.
|
