canoeboot
/
cbwww
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

remove a few stragglers from the docs 

a few stragglers from lbwww cherry picks were leftover,
referring to vendorfile insertion, but the canoeboot
build system doesn't actually do this.

Signed-off-by: Leah Rowe <leah@libreboot.org>
master
Leah Rowe 2025-01-07 19:21:21 +00:00
parent 2ea5a35d06
commit ced8eb21a7
2 changed files with 5 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
site/docs/install/latitude.md
View File

@ -36,14 +36,6 @@ known bug, but otherwise the machine will be mostly stable.
Machine-specific notes
======================
Latitude E6400
--------------
Vendor files not required for Dell Latitude E6400 if you have the Intel GPU.
If you have the Nvidia model, please use the `e6400nvidia_4mb` target, and
make sure to run the inject script.
dGPU variants
-------------

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

@ -207,21 +207,12 @@ cache/
Certain files are cached here automatically, by cbmk. The user need not touch
these files.
cache/app
--------------
When vendor updates are extracted, they go here, which is then processed to
find individual files for use in coreboot images (e.g. KBC1126 EC firmware).
This directory is constantly over-written, so it's essentially another temporary
directory used by the build system.
cache/file/
--------------
Files that are downloaded are hashed, and the cached version of the file
is stored there, named as the SHA512 checksum. This is used for vendor file
downloads, and subfile downloads.
is stored there, named as the SHA512 checksum. This is used for submodule Git
repository downloads, and subfile downloads.
A *subfile* is like a Git submodule, but it's a *file* (just a humble file),
downloaded via curl/wget. The build system does not
@ -1263,7 +1254,7 @@ Example commands:
Special commands available (not provided by files under `script/`):
./mk release
./mk -d coreboot TARGET # also downloads vendor files
./mk -d coreboot TARGET
Information about `./mk release` is written elsewhere on this page.
@ -1291,22 +1282,6 @@ These functions deal with git cloning, submodule updates, revision resets and
the application of patch files via `git am`. *Every* git repository downloaded
by cbmk is handled by the functions in this file.
include/mrc.sh
--------------
This was previously a separate script. The download logic was removed, and
now the logic under `include/vendor.sh` is used for downloads. This file now
only contains those functions used for extraction of MRC files from Google
Chromebook images, currently only used for Haswell mainboards.
This is an include, used by `include/vendor.sh`, but it's here in
this file because the vendor download script is GPLv3-only, while the MRC
extract logic in this file is GPLv2-only (forked from coreboot ages ago). Thus,
it is provided as an include to bypass license incompatibility. It has been
heavily modified to use the same style of logic and general control flow used
in the script at `include/vendor.sh`, and it is used from there.
>>>>>>> c18402c8 (update docs/maintain/)
include/lib.sh
---------------
@ -1418,15 +1393,10 @@ Example command: `./mk -b stm32-vserprog`
This also uses `rom.sh` as with the coreboot image build logic. It's all
defined in that file, so read the main section pertaining to this file.
include/vendor.sh
include/inject.sh
-----------------
Helper functions for downloading and injecting vendor files. How to use:
./mk inject ARGUMENTS
./mk -d coreboot TARGET
Refer elsewhere in the documentation for how to handle vendor files.
Functions for modifying the intel GbE MAC address on IFD-based Intel systems.
script/
=======