What the developer wrote
Authored by odudex
fix: register embed_fire in the bdftokff device list
The device was added in 26.03.0 but never listed, so glyph generation fell
through to the unmapped-device branch and printed an error on every run.
That branch happened to write the same 16px font, so the generated files
are unchanged by this.
What changed, and why it matters
This commit fixes a build-time font-generation script so that a newly supported device ('embed_fire') is recognized. Before the fix, the script printed an error but still produced the same font files. There is no security issue.
No security action needed; treat as a normal build-script fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds ‘embed_fire’ to MID_FONT_DEVICES_TO_COPY in firmware/font/bdftokff.py. The device was introduced in release 26.03.0 but omitted from this list, causing the script to fall through to an unmapped-device branch that emitted an error and wrote the same 16px font. The generated output is unchanged, so this is purely a cosmetic/logic fix in a build helper.
Changed components
firmware/font/bdftokff.pyInspect captured patch +1 / −0
diff --git a/firmware/font/bdftokff.py b/firmware/font/bdftokff.py
index 36a4824..72745f4 100644
--- a/firmware/font/bdftokff.py
+++ b/firmware/font/bdftokff.py
@@ -55,6 +55,7 @@ MID_FONT_DEVICES_TO_COPY = [
"tzt",
"wonder_k",
"yahboom_devkit",
+ "embed_fire",
]
BIG_FONT_DEVICES_TO_COPY = []
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.