alex 78bcaa79ff fix(menu): keep the countdown going after a spurious key event ...

Some firmware signals the key event without a key being available. The
simple menu then skipped the countdown for that tick, and the basic menu
started waiting for the full timeout again, so firmware that kept
signaling the key event would never boot the default entry.

Read the key inside the wait, and when no key is available keep waiting
on the same timer.

2026-09-26 20:52:15 -07:00

..

bls

feat(initrd): support chaining multiple initrds (#101)

2026-09-26 19:45:47 -07:00

boot

fix(menu): keep the countdown going after a spurious key event

2026-09-26 20:52:15 -07:00

build

chore(docs): fix all rustdoc warnings (#54)

2025-12-21 14:11:10 -08:00

config

feat(initrd): support chaining multiple initrds (#101)

2026-09-26 19:45:47 -07:00

eficore

fix(tpm): treat a full event log as a successful measurement

2026-09-26 20:52:15 -07:00

parsing

fix(autoconfigure): match arm64 Image kernels

2026-09-26 18:58:54 -07:00