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

Remove legacy "./vendor" command from docs 

We only use ./mk now.

Signed-off-by: Leah Rowe <info@minifree.org>
master
Leah Rowe 2024-12-25 08:59:53 +00:00
parent 443078014d
commit 2ac7deeefc
6 changed files with 15 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -56,7 +56,7 @@ In order to inject the necessary files into a rom image, run the script from the
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple. If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
Run the injection script pointing to the release archive you downloaded: Run the injection script pointing to the release archive you downloaded:
./vendor inject libreboot-RELEASE_targetname.tar.xz ./mk inject libreboot-RELEASE_targetname.tar.xz
The script can automatically detect the board as long as you do not change the file name. The script can automatically detect the board as long as you do not change the file name.
You can then find flash-ready ROMs in `/bin/release/` You can then find flash-ready ROMs in `/bin/release/`
@ -82,12 +82,12 @@ Alternatively, you may patch only a single rom file, but you must supply the
correct board target name as alluded to above. correct board target name as alluded to above.
For example: For example:
./vendor inject -r x230_libreboot.rom -b x230_12mb ./mk inject -r x230_libreboot.rom -b x230_12mb
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag. Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
For example: For example:
./vendor inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd ./mk inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd
You are *strongly* advised to inject the tarballs instead. However, so long as You are *strongly* advised to inject the tarballs instead. However, so long as
you're careful, injecting into single ROM images is perfectly safe. Just know you're careful, injecting into single ROM images is perfectly safe. Just know

6
site/docs/install/t420_external.md
View File

@ -25,19 +25,19 @@ In order to inject the necessary files into a rom image, run the script from the
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple. If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
Run the injection script pointing to the release archive you downloaded: Run the injection script pointing to the release archive you downloaded:
./vendor inject /path/to/libreboot-20230423_t420_8mb.tar.xz ./mk inject /path/to/libreboot-20230423_t420_8mb.tar.xz
The script can automatically detect the board as long as you do not change the file name. The script can automatically detect the board as long as you do not change the file name.
You can then find flash-ready ROMs in `/bin/release/` You can then find flash-ready ROMs in `/bin/release/`
Alternatively, you may patch only a single rom file. Alternatively, you may patch only a single rom file.
./vendor inject -r t420_libreboot.rom -b t420_8mb ./mk inject -r t420_libreboot.rom -b t420_8mb
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag. Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
For example: For example:
./vendor inject -r t420_libreboot.rom -b t420_8mb -m 00:f6:f0:40:71:fd ./mk inject -r t420_libreboot.rom -b t420_8mb -m 00:f6:f0:40:71:fd
Disassembly Disassembly
----------- -----------

6
site/docs/install/t440p_external.md
View File

@ -40,7 +40,7 @@ In order to inject the necessary files into a rom image, run the script from the
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple. If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
Run the injection script pointing to the release archive you downloaded: Run the injection script pointing to the release archive you downloaded:
./vendor inject /path/to/libreboot-RELEASE_targetname.tar.xz ./mk inject /path/to/libreboot-RELEASE_targetname.tar.xz
The script can automatically detect the board as long as you do not change the file name. The script can automatically detect the board as long as you do not change the file name.
You can then find flash-ready ROMs in `/bin/release/` You can then find flash-ready ROMs in `/bin/release/`
@ -48,12 +48,12 @@ You can then find flash-ready ROMs in `/bin/release/`
Alternatively, you may patch only a single rom file. Alternatively, you may patch only a single rom file.
For example: For example:
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb ./mk inject -r t440p_libreboot.rom -b t440plibremrc_12mb
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag. Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
For example: For example:
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb -m 00:f6:f0:40:71:fd ./mk inject -r t440p_libreboot.rom -b t440plibremrc_12mb -m 00:f6:f0:40:71:fd
NOTE: this makes use of `nvmutil`, which you can read more about in NOTE: this makes use of `nvmutil`, which you can read more about in
the [nvmutil documentation](nvmutil.md). the [nvmutil documentation](nvmutil.md).

6
site/docs/install/w541_external.md
View File

@ -43,7 +43,7 @@ In order to inject the necessary files into a rom image, run the script from the
If you only wish to flash a release rom then the process of injecting the necessary files is quite simple. If you only wish to flash a release rom then the process of injecting the necessary files is quite simple.
Run the injection script pointing to the release archive you downloaded: Run the injection script pointing to the release archive you downloaded:
./vendor inject /path/to/libreboot-RELEASE_targetname.tar.xz ./mk inject /path/to/libreboot-RELEASE_targetname.tar.xz
The script can automatically detect the board as long as you do not change the file name. The script can automatically detect the board as long as you do not change the file name.
You can then find flash-ready ROMs in `/bin/release/` You can then find flash-ready ROMs in `/bin/release/`
@ -51,12 +51,12 @@ You can then find flash-ready ROMs in `/bin/release/`
Alternatively, you may patch only a single rom file. Alternatively, you may patch only a single rom file.
For example: For example:
./vendor inject -r w541_libreboot.rom -b w541_12mb ./mk inject -r w541_libreboot.rom -b w541_12mb
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag. Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
For example: For example:
./vendor inject -r w541_libreboot.rom -b w541_12mb -m 00:f6:f0:40:71:fd ./mk inject -r w541_libreboot.rom -b w541_12mb -m 00:f6:f0:40:71:fd
NOTE: this makes use of `nvmutil`, which you can read more about in NOTE: this makes use of `nvmutil`, which you can read more about in
the [nvmutil documentation](nvmutil.md). the [nvmutil documentation](nvmutil.md).

6
site/docs/install/x230_external.md
View File

@ -36,7 +36,7 @@ The script can determine the board automatically if you have not changed the nam
In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image. In order to inject the necessary files into a rom image, run the script from the root of lbmk and point to the rom image.
Run the injection script pointing to the release archive you downloaded: Run the injection script pointing to the release archive you downloaded:
./vendor inject /path/to/libreboot-20230319-18-g9f76c92_t440_12mb.tar.xz ./mk inject /path/to/libreboot-20230319-18-g9f76c92_t440_12mb.tar.xz
The script can automatically detect the board as long as you do not change the file name. The script can automatically detect the board as long as you do not change the file name.
You can then find flash-ready ROMs in `/bin/release/` You can then find flash-ready ROMs in `/bin/release/`
@ -44,12 +44,12 @@ You can then find flash-ready ROMs in `/bin/release/`
Alternatively, you may patch only a single rom file. Alternatively, you may patch only a single rom file.
For example: For example:
./vendor inject -r x230_libreboot.rom -b x230_12mb ./mk inject -r x230_libreboot.rom -b x230_12mb
Optionally, you can use this script to modify the mac address of the rom with the `-m` flag. Optionally, you can use this script to modify the mac address of the rom with the `-m` flag.
For example: For example:
./vendor inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd ./mk inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd
NOTE: this makes use of `nvmutil`, which you can read more about in NOTE: this makes use of `nvmutil`, which you can read more about in
the [nvmutil documentation](nvmutil.md). the [nvmutil documentation](nvmutil.md).

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

@ -1329,13 +1329,6 @@ Special commands available (not provided by files under `script/`):
./mk inject ./mk inject
./mk -d coreboot TARGET # also downloads vendor files ./mk -d coreboot TARGET # also downloads vendor files
The `vendor` commands are handled by the `build` script, calling functions
inside `include/vendor.sh`, and the `./mk release` logic is handled
directly by the `build` script.
More information about `./vendor` commands can be found
here: [inserting vendor files](../install/ivy_has_internal.md)
Information about `./mk release` is written elsewhere on this page. Information about `./mk release` is written elsewhere on this page.
You can also know what build system revision you have by running: You can also know what build system revision you have by running: