File site/docs/hardware/ga-g41m-es2l.md changed (mode: 100644) (index c45afb7..3cf3e7e) |
... |
... |
image is named `libreboot.rom` for your board. You can find cbfstool |
79 |
79 |
under `cbutils/` after running the following command |
under `cbutils/` after running the following command |
80 |
80 |
in the build system: |
in the build system: |
81 |
81 |
|
|
82 |
|
./update trees -b coreboot utils |
|
|
82 |
|
./update trees -d coreboot TREENAME |
83 |
83 |
|
|
84 |
84 |
You can learn more about using the build system, lbmk, here:\ |
You can learn more about using the build system, lbmk, here:\ |
85 |
85 |
[libreboot build instructions](../build/) |
[libreboot build instructions](../build/) |
File site/docs/install/ivy_has_common.md changed (mode: 100644) (index 7564261..0bff56e) |
... |
... |
You *must* ensure that the files were inserted. |
110 |
110 |
|
|
111 |
111 |
Some examples of how to do that in lbmk: |
Some examples of how to do that in lbmk: |
112 |
112 |
|
|
113 |
|
./update trees -b coreboot utils |
|
|
113 |
|
./update trees -d coreboot TREENAME |
114 |
114 |
|
|
115 |
115 |
Now you find `cbutitls/default`, which is a directory containing `cbfstool` |
Now you find `cbutitls/default`, which is a directory containing `cbfstool` |
116 |
116 |
and `ifdtool`. Do this on your ROM image (`libreboot.rom` in the example |
and `ifdtool`. Do this on your ROM image (`libreboot.rom` in the example |
File site/docs/install/ivy_has_common.uk.md changed (mode: 100644) (index 03f54c9..d001dee) |
... |
... |
You *must* ensure that the files were inserted. |
114 |
114 |
|
|
115 |
115 |
Some examples of how to do that in lbmk: |
Some examples of how to do that in lbmk: |
116 |
116 |
|
|
117 |
|
./update trees -b coreboot utils |
|
|
117 |
|
./update trees -d coreboot TREENAME |
118 |
118 |
|
|
119 |
119 |
Now you find `cbutitls/default`, which is a directory containing `cbfstool` |
Now you find `cbutitls/default`, which is a directory containing `cbfstool` |
120 |
120 |
and `ifdtool`. Do this on your ROM image (`libreboot.rom` in the example |
and `ifdtool`. Do this on your ROM image (`libreboot.rom` in the example |
File site/docs/maintain/index.md changed (mode: 100644) (index 3938342..23e421e) |
... |
... |
Basic command: `./update trees FLAG projectname` |
1326 |
1326 |
Special operation: for building coreboot utilities `cbfstool` and `ifdtool` to |
Special operation: for building coreboot utilities `cbfstool` and `ifdtool` to |
1327 |
1327 |
go under `cbutils/`, do this: |
go under `cbutils/`, do this: |
1328 |
1328 |
|
|
1329 |
|
./update trees -b coreboot utils |
|
|
1329 |
|
./update trees -d coreboot TREENAME |
1330 |
1330 |
|
|
1331 |
1331 |
Or define specific coreboot tree such as: |
Or define specific coreboot tree such as: |
1332 |
1332 |
|
|
1333 |
|
./update trees -b coreboot utils default |
|
1334 |
|
./update trees -b coreboot utils cros |
|
|
1333 |
|
./update trees -d coreboot default |
|
1334 |
|
./update trees -d coreboot cros |
1335 |
1335 |
|
|
1336 |
1336 |
FLAG values are (only *one* to be used at a time): |
FLAG values are (only *one* to be used at a time): |
1337 |
1337 |
|
|
|
... |
... |
Example commands: |
1365 |
1365 |
./update trees -u seabios |
./update trees -u seabios |
1366 |
1366 |
./update trees -m u-boot gru_bob |
./update trees -m u-boot gru_bob |
1367 |
1367 |
./update trees -f coreboot |
./update trees -f coreboot |
1368 |
|
./update trees -b coreboot utils default |
|
1369 |
|
./update trees -b coreboot utils |
|
|
1368 |
|
./update trees -d coreboot default |
|
1369 |
|
./update trees -d coreboot |
1370 |
1370 |
|
|
1371 |
1371 |
NOTE: the `-x` and `-c` options will cause an exit with zero status, when |
NOTE: the `-x` and `-c` options will cause an exit with zero status, when |
1372 |
1372 |
the target's corresponding source tree is unavailable; a non-zero status is |
the target's corresponding source tree is unavailable; a non-zero status is |