From 2ac7deeefc4fdafecb4ba23a3dce271637f9a75a Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Wed, 25 Dec 2024 08:59:53 +0000 Subject: [PATCH] Remove legacy "./vendor" command from docs We only use ./mk now. Signed-off-by: Leah Rowe --- site/docs/install/ivy_has_common.md | 6 +++--- site/docs/install/t420_external.md | 6 +++--- site/docs/install/t440p_external.md | 6 +++--- site/docs/install/w541_external.md | 6 +++--- site/docs/install/x230_external.md | 6 +++--- site/docs/maintain/index.md | 7 ------- 6 files changed, 15 insertions(+), 22 deletions(-) diff --git a/site/docs/install/ivy_has_common.md b/site/docs/install/ivy_has_common.md index a416393..0fb7b51 100644 --- a/site/docs/install/ivy_has_common.md +++ b/site/docs/install/ivy_has_common.md @@ -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. 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. 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. 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. 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're careful, injecting into single ROM images is perfectly safe. Just know diff --git a/site/docs/install/t420_external.md b/site/docs/install/t420_external.md index b7b9536..9ff3d32 100644 --- a/site/docs/install/t420_external.md +++ b/site/docs/install/t420_external.md @@ -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. 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. You can then find flash-ready ROMs in `/bin/release/` 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. 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 ----------- diff --git a/site/docs/install/t440p_external.md b/site/docs/install/t440p_external.md index 8c54780..d10fdc9 100644 --- a/site/docs/install/t440p_external.md +++ b/site/docs/install/t440p_external.md @@ -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. 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. 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. 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. 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 the [nvmutil documentation](nvmutil.md). diff --git a/site/docs/install/w541_external.md b/site/docs/install/w541_external.md index b7480fa..4f49f46 100644 --- a/site/docs/install/w541_external.md +++ b/site/docs/install/w541_external.md @@ -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. 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. 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. 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. 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 the [nvmutil documentation](nvmutil.md). diff --git a/site/docs/install/x230_external.md b/site/docs/install/x230_external.md index 814db86..8bbc59e 100644 --- a/site/docs/install/x230_external.md +++ b/site/docs/install/x230_external.md @@ -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. 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. 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. 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. 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 the [nvmutil documentation](nvmutil.md). diff --git a/site/docs/maintain/index.md b/site/docs/maintain/index.md index c2477a9..292ae01 100644 --- a/site/docs/maintain/index.md +++ b/site/docs/maintain/index.md @@ -1329,13 +1329,6 @@ Special commands available (not provided by files under `script/`): ./mk inject ./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. You can also know what build system revision you have by running: