File site/docs/install/ivy_has_common.md changed (mode: 100644) (index a416393..0fb7b51) |
... |
... |
In order to inject the necessary files into a rom image, run the script from the |
56 |
56 |
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. |
57 |
57 |
Run the injection script pointing to the release archive you downloaded: |
Run the injection script pointing to the release archive you downloaded: |
58 |
58 |
|
|
59 |
|
./vendor inject libreboot-RELEASE_targetname.tar.xz |
|
|
59 |
|
./mk inject libreboot-RELEASE_targetname.tar.xz |
60 |
60 |
|
|
61 |
61 |
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. |
62 |
62 |
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, but you must supply the |
82 |
82 |
correct board target name as alluded to above. |
correct board target name as alluded to above. |
83 |
83 |
For example: |
For example: |
84 |
84 |
|
|
85 |
|
./vendor inject -r x230_libreboot.rom -b x230_12mb |
|
|
85 |
|
./mk inject -r x230_libreboot.rom -b x230_12mb |
86 |
86 |
|
|
87 |
87 |
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. |
88 |
88 |
For example: |
For example: |
89 |
89 |
|
|
90 |
|
./vendor inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd |
|
|
90 |
|
./mk inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd |
91 |
91 |
|
|
92 |
92 |
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 |
93 |
93 |
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 |
File site/docs/install/t420_external.md changed (mode: 100644) (index b7b9536..9ff3d32) |
... |
... |
In order to inject the necessary files into a rom image, run the script from the |
25 |
25 |
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. |
26 |
26 |
Run the injection script pointing to the release archive you downloaded: |
Run the injection script pointing to the release archive you downloaded: |
27 |
27 |
|
|
28 |
|
./vendor inject /path/to/libreboot-20230423_t420_8mb.tar.xz |
|
|
28 |
|
./mk inject /path/to/libreboot-20230423_t420_8mb.tar.xz |
29 |
29 |
|
|
30 |
30 |
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. |
31 |
31 |
You can then find flash-ready ROMs in `/bin/release/` |
You can then find flash-ready ROMs in `/bin/release/` |
32 |
32 |
|
|
33 |
33 |
Alternatively, you may patch only a single rom file. |
Alternatively, you may patch only a single rom file. |
34 |
34 |
|
|
35 |
|
./vendor inject -r t420_libreboot.rom -b t420_8mb |
|
|
35 |
|
./mk inject -r t420_libreboot.rom -b t420_8mb |
36 |
36 |
|
|
37 |
37 |
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. |
38 |
38 |
For example: |
For example: |
39 |
39 |
|
|
40 |
|
./vendor inject -r t420_libreboot.rom -b t420_8mb -m 00:f6:f0:40:71:fd |
|
|
40 |
|
./mk inject -r t420_libreboot.rom -b t420_8mb -m 00:f6:f0:40:71:fd |
41 |
41 |
|
|
42 |
42 |
Disassembly |
Disassembly |
43 |
43 |
----------- |
----------- |
File site/docs/install/t440p_external.md changed (mode: 100644) (index 8c54780..d10fdc9) |
... |
... |
In order to inject the necessary files into a rom image, run the script from the |
40 |
40 |
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. |
41 |
41 |
Run the injection script pointing to the release archive you downloaded: |
Run the injection script pointing to the release archive you downloaded: |
42 |
42 |
|
|
43 |
|
./vendor inject /path/to/libreboot-RELEASE_targetname.tar.xz |
|
|
43 |
|
./mk inject /path/to/libreboot-RELEASE_targetname.tar.xz |
44 |
44 |
|
|
45 |
45 |
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. |
46 |
46 |
You can then find flash-ready ROMs in `/bin/release/` |
You can then find flash-ready ROMs in `/bin/release/` |
|
... |
... |
You can then find flash-ready ROMs in `/bin/release/` |
48 |
48 |
Alternatively, you may patch only a single rom file. |
Alternatively, you may patch only a single rom file. |
49 |
49 |
For example: |
For example: |
50 |
50 |
|
|
51 |
|
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb |
|
|
51 |
|
./mk inject -r t440p_libreboot.rom -b t440plibremrc_12mb |
52 |
52 |
|
|
53 |
53 |
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. |
54 |
54 |
For example: |
For example: |
55 |
55 |
|
|
56 |
|
./vendor inject -r t440p_libreboot.rom -b t440plibremrc_12mb -m 00:f6:f0:40:71:fd |
|
|
56 |
|
./mk inject -r t440p_libreboot.rom -b t440plibremrc_12mb -m 00:f6:f0:40:71:fd |
57 |
57 |
|
|
58 |
58 |
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 |
59 |
59 |
the [nvmutil documentation](nvmutil.md). |
the [nvmutil documentation](nvmutil.md). |
File site/docs/install/w541_external.md changed (mode: 100644) (index b7480fa..4f49f46) |
... |
... |
In order to inject the necessary files into a rom image, run the script from the |
43 |
43 |
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. |
44 |
44 |
Run the injection script pointing to the release archive you downloaded: |
Run the injection script pointing to the release archive you downloaded: |
45 |
45 |
|
|
46 |
|
./vendor inject /path/to/libreboot-RELEASE_targetname.tar.xz |
|
|
46 |
|
./mk inject /path/to/libreboot-RELEASE_targetname.tar.xz |
47 |
47 |
|
|
48 |
48 |
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. |
49 |
49 |
You can then find flash-ready ROMs in `/bin/release/` |
You can then find flash-ready ROMs in `/bin/release/` |
|
... |
... |
You can then find flash-ready ROMs in `/bin/release/` |
51 |
51 |
Alternatively, you may patch only a single rom file. |
Alternatively, you may patch only a single rom file. |
52 |
52 |
For example: |
For example: |
53 |
53 |
|
|
54 |
|
./vendor inject -r w541_libreboot.rom -b w541_12mb |
|
|
54 |
|
./mk inject -r w541_libreboot.rom -b w541_12mb |
55 |
55 |
|
|
56 |
56 |
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. |
57 |
57 |
For example: |
For example: |
58 |
58 |
|
|
59 |
|
./vendor inject -r w541_libreboot.rom -b w541_12mb -m 00:f6:f0:40:71:fd |
|
|
59 |
|
./mk inject -r w541_libreboot.rom -b w541_12mb -m 00:f6:f0:40:71:fd |
60 |
60 |
|
|
61 |
61 |
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 |
62 |
62 |
the [nvmutil documentation](nvmutil.md). |
the [nvmutil documentation](nvmutil.md). |
File site/docs/install/x230_external.md changed (mode: 100644) (index 814db86..8bbc59e) |
... |
... |
The script can determine the board automatically if you have not changed the nam |
36 |
36 |
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. |
37 |
37 |
Run the injection script pointing to the release archive you downloaded: |
Run the injection script pointing to the release archive you downloaded: |
38 |
38 |
|
|
39 |
|
./vendor inject /path/to/libreboot-20230319-18-g9f76c92_t440_12mb.tar.xz |
|
|
39 |
|
./mk inject /path/to/libreboot-20230319-18-g9f76c92_t440_12mb.tar.xz |
40 |
40 |
|
|
41 |
41 |
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. |
42 |
42 |
You can then find flash-ready ROMs in `/bin/release/` |
You can then find flash-ready ROMs in `/bin/release/` |
|
... |
... |
You can then find flash-ready ROMs in `/bin/release/` |
44 |
44 |
Alternatively, you may patch only a single rom file. |
Alternatively, you may patch only a single rom file. |
45 |
45 |
For example: |
For example: |
46 |
46 |
|
|
47 |
|
./vendor inject -r x230_libreboot.rom -b x230_12mb |
|
|
47 |
|
./mk inject -r x230_libreboot.rom -b x230_12mb |
48 |
48 |
|
|
49 |
49 |
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. |
50 |
50 |
For example: |
For example: |
51 |
51 |
|
|
52 |
|
./vendor inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd |
|
|
52 |
|
./mk inject -r x230_libreboot.rom -b x230_12mb -m 00:f6:f0:40:71:fd |
53 |
53 |
|
|
54 |
54 |
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 |
55 |
55 |
the [nvmutil documentation](nvmutil.md). |
the [nvmutil documentation](nvmutil.md). |
File site/docs/maintain/index.md changed (mode: 100644) (index c2477a9..292ae01) |
... |
... |
Special commands available (not provided by files under `script/`): |
1329 |
1329 |
./mk inject |
./mk inject |
1330 |
1330 |
./mk -d coreboot TARGET # also downloads vendor files |
./mk -d coreboot TARGET # also downloads vendor files |
1331 |
1331 |
|
|
1332 |
|
The `vendor` commands are handled by the `build` script, calling functions |
|
1333 |
|
inside `include/vendor.sh`, and the `./mk release` logic is handled |
|
1334 |
|
directly by the `build` script. |
|
1335 |
|
|
|
1336 |
|
More information about `./vendor` commands can be found |
|
1337 |
|
here: [inserting vendor files](../install/ivy_has_internal.md) |
|
1338 |
|
|
|
1339 |
1332 |
Information about `./mk release` is written elsewhere on this page. |
Information about `./mk release` is written elsewhere on this page. |
1340 |
1333 |
|
|
1341 |
1334 |
You can also know what build system revision you have by running: |
You can also know what build system revision you have by running: |