Releases: excavador-turing/bmcd
Release list
v2.29.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.28.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.27.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.26.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.25.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.24.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.23.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.22.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.21.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.
v2.20.0
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:
sha256sum -c SHA256SUMS
SHA256SUMS lists bare filenames, so run it from the directory
holding the tarball.