drivers/firmware/google

Google coreboot and ChromeOS firmware interfaces

Kernel-side glue for talking to firmware on machines that boot with Google's coreboot, including Chromebooks and Google's own server fleet. It exposes things like the coreboot table, the Google System Management Interface (GSMI) for logging and event handling, and related vendor firmware hooks shipping on hardware sold today.

keep conf=0.88 last_sold=2025 deploy=medium replacement=none subsystem=firmware category=firmware
88%

recommendation

It should stay because this code supports Chromebooks and Google servers that are still sold new in 2025, and upstream maintenance is clearly current — including 2024 cleanups to gsmi.c and 2026 patches reworking the coreboot table and bus code. There is no removal signal; this is living infrastructure for a large installed base.

repository signals

14 files
2,564 source lines
34 commits, 5y
+353 / −79 lines added / removed, 5y
23 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 34 total · active in 20/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 2 commits · +2 −3 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 1 commit · +1 −1 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +9 −0 2022-10: 1 commit · +29 −8 2022-11: 2 commits · +177 −3 2022-12: 0 commits · +0 −0 2023-01: 4 commits · +14 −9 2023-02: 1 commit · +0 −8 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +1 −1 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 1 commit · +3 −0 2023-12: 1 commit · +2 −3 2024-01: 0 commits · +0 −0 2024-02: 3 commits · +50 −7 2024-03: 2 commits · +9 −4 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +8 −0 2024-07: 1 commit · +3 −3 2024-08: 0 commits · +0 −0 2024-09: 1 commit · +14 −0 2024-10: 1 commit · +4 −2 2024-11: 1 commit · +1 −1 2024-12: 4 commits · +14 −14 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 2 commits · +5 −5 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 2 commits · +4 −4 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Thomas Zimmermann posted a 2026 patch in chrome-platform touching coreboot_table.c to export coreboot table entries, showing active upstream maintenance.

  2. lore.kernel.org

    A companion 2026 patch adjusts coreboot bus initialization in this directory, indicating ongoing functional cleanup rather than abandonment.

  3. lore.kernel.org

    gsmi.c received a 2024 subsystem-specific update on chrome-platform, confirming recent non-removal attention.

  4. google.com

    Google's Chromebook Plus page listed multiple Chromebook models for sale in 2025, supporting that ChromeOS/coreboot-class hardware is still sold new.

  5. git.kernel.org

    Kconfig describes these as firmware drivers for Google servers, Chromebooks, and other devices using coreboot firmware.

codex reasoning notes (technical)

Local shell inspection of Kconfig showed this directory covers Google servers, Chromebooks, and coreboot devices rather than a dead legacy niche. lore_activity on coreboot_table.c and gsmi.c returned 2026/2024 chrome-platform traffic with reviewed/acked patches, so upstream attention is current. A removal-search attempt via lore_regex timed out twice, and a fallback lei query was blocked by the local sandbox daemon restriction; with active maintenance and current-product evidence, there is no positive removal signal. Sources obtained via mcp__lore_http__.lore_activity, web.search_query/open results, local file read plus canonical recall of the kernel.org tree URL.