documented new easy use of blob injection script

hslick-master
shmalebx9 2023-04-02 20:30:13 -06:00
parent 3cd72fb81e
commit e1fc7f97d9
3 changed files with 28 additions and 0 deletions

View File

@ -74,6 +74,16 @@ Lbmk includes a script that will automatically inject the necessary blobs into a
The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag. The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag.
In order to inject the necessary blobs into a rom image, run the script from the root of lbmk and point to the rom image. In order to inject the necessary blobs into a rom image, run the script from the root of lbmk and point to the rom image.
If you only wish to flash a release rom then the process of injecting the necessary blobs is quite simple.
Run the injection script pointing to the release archive you downloaded:
./blobutil inject /path/to/libreboot-20230319-18-g9f76c92_t440pmrc_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/`
Alternatively, you may patch only a single rom file.
For example: For example:
./blobutil inject -r x230_libreboot.rom -b x230_12mb ./blobutil inject -r x230_libreboot.rom -b x230_12mb

View File

@ -21,6 +21,16 @@ Lbmk includes a script that will automatically inject the necessary blobs into a
The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag. The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag.
In order to inject the necessary blobs into a rom image, run the script from the root of lbmk and point to the rom image. In order to inject the necessary blobs into a rom image, run the script from the root of lbmk and point to the rom image.
If you only wish to flash a release rom then the process of injecting the necessary blobs is quite simple.
Run the injection script pointing to the release archive you downloaded:
./blobutil 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/`
Alternatively, you may patch only a single rom file.
For example (libre replacement of `mrc.bin`): For example (libre replacement of `mrc.bin`):
./blobutil inject -r t440p_libreboot.rom -b t440p_12mb ./blobutil inject -r t440p_libreboot.rom -b t440p_12mb

View File

@ -25,6 +25,14 @@ Lbmk includes a script that will automatically inject the necessary blobs into a
The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag. The script can determine the board automatically if you have not changed the name, but you can also manually set the board name with the `-b` flag.
In order to inject the necessary blobs into a rom image, run the script from the root of lbmk and point to the rom image. In order to inject the necessary blobs 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:
./blobutil 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/`
Alternatively, you may patch only a single rom file.
For example: For example:
./blobutil inject -r x230_libreboot.rom -b x230_12mb ./blobutil inject -r x230_libreboot.rom -b x230_12mb