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

update the maintenance manual 

it's not a big issue, but there were a few minor
inaccuracies here, left over after the last audit.

Signed-off-by: Leah Rowe <leah@libreboot.org>
master
Leah Rowe 2023-10-22 00:13:48 +01:00
parent aee0da2bea
commit 239ef69956
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/docs/build/index.md vendored
View File

@ -203,7 +203,7 @@ re-inserted (e.g. KBC1126 EC firmware on HP EliteBooks). Please read this page
for context:
<https://libreboot.org/docs/install/ivy_has_common.html>
The scripts under directory `script/update/vendor/` are the ones that do this.
The scripts under directory `script/vendor/` are the ones that do this.
Specifically, `script/vendor/download`. The benefit of this is that you
do not need to extract anything from the original vendor image (e.g. Lenovo
UEFI image).

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

@ -348,7 +348,7 @@ may not have much RAM.
Where large files (or a large number of files) are handled by lbmk on a
temporary basis, this `tmp/` directory is created and then used.
vendor/
vendorfiles/
---------------
Used by the vendor file handler scripts, referenced in certain coreboot configs.
@ -1036,7 +1036,13 @@ update
---------------
Symbolic link, pointing to the `build` script. This is executed by the user, or
by lbmk, referencing scripts under `script/update/*/`.
by lbmk, referencing scripts under `script/update/`.
vendor
---------------
Symbolic link, pointing to the `build` script. This is executed by the user, or
by lbmk, referincing scripts under `script/vendor/`
include/
===============
@ -1095,7 +1101,7 @@ in the script at `script/vendor/download`, and it is used from there.
include/option.sh
---------------
Functions used by scripts under `script/update/vendor/`, for checking defconfig
Functions used by scripts under `script/vendor/`, for checking defconfig
files. These files are checked because the scripts need to know whether a given
file is used; if it is, a path is then specified in defconfig, telling the vendor
script either where it is, or where it should be downloaded to.