drivers/video/fbdev/savage

S3 Savage, ProSavage, SuperSavage, and Twister framebuffer

Framebuffer support for S3's Savage line of PCI and AGP graphics chips from the late 1990s and early 2000s, including the discrete Savage3D, Savage4, and Savage 2000 desktop and notebook GPUs as well as the VIA-integrated ProSavage, SuperSavage, and Twister chipsets that shipped in budget laptops and motherboards through about 2004.

keep-annotate conf=0.81 last_sold=2004 deploy=low replacement=none subsystem=video category=graphics-display
81%

recommendation

Worth keeping but documenting its niche, because the hardware has been out of production for two decades yet the code is still seeing the occasional real bug-fix patch (an EDID cleanup leak fix in 2026 and another functional fix from a Huawei contributor in 2024). It remains configurable in current kernels and serves a small population of retro and legacy machines, so removal would be premature even though new deployments are essentially nil.

repository signals

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

sources

  1. lore.kernel.org

    As of April 20, 2026, savagefb still receives targeted bug-fix patches upstream ('fix probe-path EDID cleanup leaks').

  2. lore.kernel.org

    The driver also received a functional fix in April 2024, indicating non-zero maintenance rather than pure bitrot.

  3. cateee.net

    CONFIG_FB_SAVAGE remains present in current kernels; LKDDb describes it as support for notebooks and computers with S3 Savage PCI/AGP chips and lists the supported PCI IDs.

  4. en.wikipedia.org

    The Savage family was introduced in 1998-1999; discrete Savage products were discontinued after S3's 2001 sale to VIA, with later usage limited to integrated ProSavage/Twister/SuperSavage-era designs that were later superseded by UniChrome.

codex reasoning notes (technical)

Local shell inspection (`rg` in the directory) confirmed this is the `savagefb` PCI framebuffer driver and showed covered chip names including Savage3D/4/2000, ProSavage, SuperSavage, and Twister. `lore_file_timeline` on `savagefb_driver.c` produced the 2026 and 2024 lore URLs, which show recent bug-fix traffic and no evidence here of an active removal push, so removal/deprecation would be premature. Web search + open on LKDDb confirmed the driver is still configurable upstream and targets old PCI/AGP notebook/desktop GPUs. Web search + open on Wikipedia provided the product-family timeline; `last_widely_available_year=2004` is an inference from discrete Savage ending by 2001 and remaining VIA-integrated derivatives being later superseded, so present-day deployment is best characterized as low legacy use rather than none.