You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The full build also includes: lvm2, tpm2-tools, flashrom/flashprog, dropbear (SSH),
109
114
fbwhiptail (GUI), qrencode, and many others. See individual `modules/*` files and
@@ -118,12 +123,13 @@ kernel.
118
123
119
124
* Building coreboot's cross compilers can take a while. Luckily this is only done once.
120
125
* Builds are finally reproducible! The [reproduciblebuilds tag](https://github.com/osresearch/heads/issues?q=is%3Aopen+is%3Aissue+milestone%3Areproduciblebuilds) tracks any regressions.
121
-
* Currently only tested in QEMU, the Thinkpad x230, Librem series and the Chell Chromebook.
122
-
** Xen does not work in QEMU. Signing, HOTP, and TOTP do work; see below.
123
-
* Building for the Lenovo X220 requires binary blobs to be placed in the blobs/x220/ folder.
124
-
See the readme.md file in that folder
125
-
* Building for the Librem 13 v2/v3 or Librem 15 v3/v4 requires binary blobs to be placed in
126
-
the blobs/librem_skl folder. See the readme.md file in that folder
126
+
* Current tested and maintained boards are tracked in [doc/BOARDS_AND_TESTERS.md](doc/BOARDS_AND_TESTERS.md). Board targets themselves live under `boards/`.
127
+
* Xen does not work in QEMU. Signing, HOTP, and TOTP do work; see below.
128
+
* Blob requirements are board- or board-family-specific. Check the relevant documentation under `blobs/` for the target you are building.
129
+
* Purism boards use Purism-managed coreboot blob paths from the Purism fork (for example `3rdparty/purism-blobs/...` via `CONFIG_IFD_BIN_PATH` and `CONFIG_ME_BIN_PATH` in `config/coreboot-librem_*.config`). Heads should not maintain those vendor blob payloads. Runtime firmware notes for Librem blob jail are in [blobs/librem_jail/README](blobs/librem_jail/README).
130
+
* Lenovo xx20 boards such as X220 and X230 use the shared xx20 blob flow documented in [blobs/xx20/readme.md](blobs/xx20/readme.md). X220-specific notes are in [blobs/x220/readme.md](blobs/x220/readme.md).
131
+
* Other boards can source blobs from board-family directories under `blobs/` (for example xx20/xx30/xx80, t420, t440p, w541) or from fork-specific paths configured in coreboot configs (for example Dasharo boards using `3rdparty/dasharo-blobs/...`). Vendor blob payloads remain maintained by their upstream vendors/forks.
132
+
* T480 and T480s blob requirements are documented in [blobs/xx80/README.md](blobs/xx80/README.md). Other families have their own docs under `blobs/`, for example `t420/`, `t440p/`, and `w541/`.
0 commit comments