drivers/video/fbdev/kyro

STMicroelectronics Kyro and Kyro II PowerVR3 framebuffer

Framebuffer support for the STMicroelectronics STG4000-based "Kyro" and "Kyro II" PCI/AGP graphics cards, a PowerVR Series 3 consumer 3D graphics family sold around 2000-2001 under names like the Hercules 3D Prophet Kyro. The cards competed briefly with early GeForce and Radeon parts before STMicro exited the PC graphics market.

keep-annotate conf=0.77 last_sold=2001 deploy=low replacement=none subsystem=video category=graphics-display
77%

recommendation

Worth keeping but flagging as a niche legacy driver. The hardware was last widely sold in 2001 and today survives mainly in retro PC collections, yet the code is not abandoned: real bug-fix patches landed as recently as March and July 2025, so removing it would cut off the small but active community of users still running these cards. Documenting it as retro-only would set expectations without disrupting that maintenance.

repository signals

8 files
2,415 source lines
14 commits, 5y
+41 / −23 lines added / removed, 5y
5 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 14 total · active in 10/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 · +8 −0 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: 0 commits · +0 −0 2022-03: 1 commit · +1 −1 2022-04: 1 commit · +2 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 1 commit · +5 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 1 commit · +5 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +1 −1 2023-06: 0 commits · +0 −0 2023-07: 2 commits · +5 −6 2023-08: 1 commit · +1 −3 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 1 commit · +1 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 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: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 3 commits · +12 −12 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: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The driver received substantive upstream maintenance in July 2025 ('Add missing PCI memory region request'), so it is not completely dormant.

  2. lore.kernel.org

    The driver also received a bug-fix style patch in March 2025 ('Add some geometry checks'), indicating real bug-fix traffic rather than pure treewide churn.

  3. cateee.net

    LKDDb maps CONFIG_FB_KYRO to the kyrofb driver and PCI ID 104a:0010 (STG4000 / 3D Prophet Kyro Series), confirming the hardware scope is a single legacy PCI graphics family.

  4. en.wikipedia.org

    PowerVR documentation summary places the STG4000 Kyro generation in 2000, with Kyro II following in 2001, supporting that this is early-2000s consumer graphics hardware rather than current product.

codex reasoning notes (technical)

Obsolete early-2000s PCI/AGP graphics hardware, with no evidence from the gathered results that boards are sold new in 2025; current use is most plausibly retro/collector systems, so deployments are low. However, lore history shows genuine maintenance in 2025, which argues against deprecate/remove despite the age of the hardware. No natural hardware-specific upstream successor is evident for this PCI ID, so replacement_driver is null. Source acquisition: the two lore.kernel.org URLs came directly from `lore_file_timeline`; the LKDDb and Wikipedia URLs came from `web.search_query` results. A precise `lei` subject query for removal discussion could not run in this sandbox, and a broad lore regex timed out, so absence of removal talk is an inference from the successful lore evidence rather than a proven negative.