Infrastructure inside the kernel's driver core that lets firmware blobs be compiled directly into the kernel image, so that drivers needing firmware can find it during early boot before any filesystem is available. It is plumbing used by many drivers, not a driver for any particular piece of hardware.
This is not actually a driver directory; it is part of the firmware loading framework that lets vendors embed firmware images into a kernel build. It supports other drivers rather than controlling hardware itself, so the keep/remove question does not apply.
repository signals
2files
106source lines
5commits, 5y
+113 / −6lines added / removed, 5y
3authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 5 total · active in 4/61 months
sources
No sources cited.
codex reasoning notes (technical)
Not a driver directory: built-in firmware loader support code under the driver core, not kernel-bound hardware driver code.