libreboot
/
lbwww
1
0
Fork 0
Code Packages Projects Releases Activity

document utils command change 

Signed-off-by: Leah Rowe <info@minifree.org>
master
Leah Rowe 2024-07-23 02:49:08 +01:00
parent c2f9253c45
commit 3703d3737c
5 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/docs/hardware/ga-g41m-es2l.md
View File

@ -79,7 +79,7 @@ image is named `libreboot.rom` for your board. You can find cbfstool
under `cbutils/` after running the following command under `cbutils/` after running the following command
in the build system: in the build system:
./update trees -b coreboot utils ./update trees -d coreboot TREENAME
You can learn more about using the build system, lbmk, here:\ You can learn more about using the build system, lbmk, here:\
[libreboot build instructions](../build/) [libreboot build instructions](../build/)

2
site/docs/install/ivy_has_common.md
View File

@ -110,7 +110,7 @@ You *must* ensure that the files were inserted.
Some examples of how to do that in lbmk: Some examples of how to do that in lbmk:
./update trees -b coreboot utils ./update trees -d coreboot TREENAME
Now you find `cbutitls/default`, which is a directory containing `cbfstool` Now you find `cbutitls/default`, which is a directory containing `cbfstool`
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

2
site/docs/install/ivy_has_common.uk.md
View File

@ -114,7 +114,7 @@ You *must* ensure that the files were inserted.
Some examples of how to do that in lbmk: Some examples of how to do that in lbmk:
./update trees -b coreboot utils ./update trees -d coreboot TREENAME
Now you find `cbutitls/default`, which is a directory containing `cbfstool` Now you find `cbutitls/default`, which is a directory containing `cbfstool`
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

2
site/docs/linux/grub_hardening.md
View File

@ -83,7 +83,7 @@ image:
You can build `cbfstool` in the libreboot build system. Run this command: You can build `cbfstool` in the libreboot build system. Run this command:
./update trees -b coreboot utils ./update trees -d coreboot TREENAME
This assumes that you already downloaded coreboot: This assumes that you already downloaded coreboot:

10
site/docs/maintain/index.md
View File

@ -1326,12 +1326,12 @@ Basic command: `./update trees FLAG projectname`
Special operation: for building coreboot utilities `cbfstool` and `ifdtool` to Special operation: for building coreboot utilities `cbfstool` and `ifdtool` to
go under `cbutils/`, do this: go under `cbutils/`, do this:
./update trees -b coreboot utils ./update trees -d coreboot TREENAME
Or define specific coreboot tree such as: Or define specific coreboot tree such as:
./update trees -b coreboot utils default ./update trees -d coreboot default
./update trees -b coreboot utils cros ./update trees -d coreboot cros
FLAG values are (only *one* to be used at a time): FLAG values are (only *one* to be used at a time):
@ -1365,8 +1365,8 @@ Example commands:
./update trees -u seabios ./update trees -u seabios
./update trees -m u-boot gru_bob ./update trees -m u-boot gru_bob
./update trees -f coreboot ./update trees -f coreboot
./update trees -b coreboot utils default ./update trees -d coreboot default
./update trees -b coreboot utils ./update trees -d coreboot
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
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