bmcd¶
The daemon: the API, the update logic, the metrics.
Newest release v2.29.0, 24 in total. Every entry is the release note as published on GitHub, fetched by just refresh-changelog — not written here, so the two cannot disagree.
v2.29.0 — 10 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
openapi.json is this daemon's own description of its API,
emitted by the binary that implements it, so it describes this
release and no other. A board serves the same document at
GET /api/bmc/openapi.json.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.28.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
openapi.json is this daemon's own description of its API,
emitted by the binary that implements it, so it describes this
release and no other. A board serves the same document at
GET /api/bmc/openapi.json.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.27.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
openapi.json is this daemon's own description of its API,
emitted by the binary that implements it, so it describes this
release and no other. A board serves the same document at
GET /api/bmc/openapi.json.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.26.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
openapi.json is this daemon's own description of its API,
emitted by the binary that implements it, so it describes this
release and no other. A board serves the same document at
GET /api/bmc/openapi.json.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.25.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.24.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.23.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.22.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.21.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.19.1 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.20.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.19.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.18.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.17.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.16.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.15.1 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.15.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.14.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.13.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.12.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.11.0 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.10.1 — 09 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.10.0 — 08 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.
v2.9.0 — 08 September 2026
bmcd built from the hive branch of this fork, for the Turing Pi 2
BMC firmware build to consume.
Not a Turing Pi release. The firmware pins this repository by commit and compiles it inside Buildroot, so no binary is published here -- a binary built by this runner would not match the board's toolchain. The tarball is the source that was tagged.
Verify with:
SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.