diff --git a/site/docs/install/e6400.md b/site/docs/install/e6400.md index fc59209..5b9c4f0 100644 --- a/site/docs/install/e6400.md +++ b/site/docs/install/e6400.md @@ -158,24 +158,6 @@ codeberg](https://codeberg.org/libreboot/lbmk/issues/14#issuecomment-907758). How to flash internally (no diassembly) ======================================= -Warning for BSD users ---------------------- - -**NOTE (15 October 2023): The util is now called `dell-flash-unlock`, but it -was previously called `e6400-flash-unlock`. Links have been updated.** - -BSD *boots* and works properly on these machines, but take note: - -Nicholas's [dell-flash-unlock](https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/dell_flash_unlock.c) -utility has been ported to OpenBSD, but *other* BSDs are assumed unsupported for -now. - -NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog) -now, as of 27 January 2024, which is a fork of flashrom. - -NOTE: BSD is mentioned above, but the only BSD tested for `dell-flash-unlock` -is OpenBSD, as of 15 October 2023. - Flashing from Linux ------------------- diff --git a/site/docs/linux/index.md b/site/docs/linux/index.md index ef30b2e..bb17991 100644 --- a/site/docs/linux/index.md +++ b/site/docs/linux/index.md @@ -46,6 +46,11 @@ Then still as root, do these commands: export PATH="$PATH:/sbin" update-grub +NOTE: `update-grub` is very much Debian-centric. Not all distros will have it. +On Arch-based distros for instance, you might do: + + grub-mkconfig -o /boot/grub/grub.cfg + Now your distro's GRUB menu should work, when your distro's GRUB bootloader is executed from Libreboot's SeaBIOS payload. diff --git a/site/docs/maintain/index.md b/site/docs/maintain/index.md index b1e660d..69a1aba 100644 --- a/site/docs/maintain/index.md +++ b/site/docs/maintain/index.md @@ -139,8 +139,8 @@ This directory is created when running any of the following commands, with the right arguments: ./build roms ARGUMENTS_HERE - ./build serprog stm32 - ./build serprog rp2040 + ./build roms serprog stm32 + ./build roms serprog rp2040 Simply speaking, `bin/` shall contain finished ROM images or firmware, that can then be installed (flashed) to the target device. @@ -1117,27 +1117,6 @@ This directory contains *helper scripts*, to be included by main scripts using the `.` command (called the `source` command in `bash`, but we rely upon posix `sh` only). -include/err.sh ---------------- - -Generic error handling, used by all lbmk scripts. - -This also contains functions to verify the current libreboot version, and check -whether Git is properly initialised on the host system. It also contains -the `setvars` function, which provides a shorthand way of initialising many -variables (combined with use of `eval`), which lbmk uses heavily. - -This function also contains `x_` and `xx_` which lbmk uses to execute commands -and ensure that they cause an exit (with non-zero status) from lbmk, if they -return an error state; the `xx_` function calls `fail()` which a script must -provide, to perform some action before calling `err` which in turn prints an -error message provided as argument. It is used similarly to the C -function `err()` in BSD libc. The `x_` function simply calls `err`. - -This entire file is heavily inspired by `err.h` in BSD libc code. This file is -heavily used by lbmk (it's used by every script), to provide clean error -handling in `sh`. - include/git.sh -------------- @@ -1178,6 +1157,17 @@ possible, and contains miscallaneous functions that don't belong anywhere else. The functions here are mostly those that deal with configuration files; scanning them to set variables and so on. +This file also contains generic error handling, used by all lbmk scripts. + +This also contains functions to verify the current libreboot version, and check +whether Git is properly initialised on the host system. It also contains +the `setvars` function, which provides a shorthand way of initialising many +variables (combined with use of `eval`), which lbmk uses heavily. + +This function also contains `x_()` which lbmk uses to execute commands +and ensure that they cause an exit (with non-zero status) from lbmk, if they +return an error state. + script/ ======= @@ -1286,18 +1276,19 @@ When the ROM is finished compiling, it will appear under a directory in `bin/` This script is the beating heart of Libreboot. Break it, and you break Libreboot! -### script/build/serprog +Serprog images: Build firmware images for serprog-based SPI programmers, where they use an STM32 MCU. It also builds for RP2040-based programmers like Raspberry Pi Pico. -Example command: `./build serprog stm32` +Example command: `./build roms serprog stm32` -Example command: `./build serprog rp2040` +Example command: `./build roms serprog rp2040` The `list` argument is available: - ./build serprog stm32 list + ./build roms serprog stm32 list + ./build roms serprog rp2040 list Without arguments, all targets would be compiled, but you can specify a short list of targets instead, based on the output of `list`. diff --git a/site/tasks/index.md b/site/tasks/index.md index 6d721dc..8c31704 100644 --- a/site/tasks/index.md +++ b/site/tasks/index.md @@ -2209,3 +2209,8 @@ page 89 also + +ec hacking on lenovo x230 +========================= + +