drivers/video/fbdev

Legacy framebuffer (fbdev) display drivers

The original Linux framebuffer subsystem, providing a simple linear pixel buffer interface for graphics hardware ranging from 1990s workstation cards (like DEC TGA) and embedded LCD controllers to modern firmware-provided framebuffers such as the EFI boot console on current UEFI PCs. It predates today's DRM/KMS graphics stack and is what /dev/fb0 has historically pointed at.

keep-annotate conf=0.84 last_sold=2025 deploy=medium replacement=DRM/KMS drivers with DRM fbdev emulation (CONFIG_DRM_FBDEV_EMULATION) subsystem=video category=graphics-display
84%

recommendation

Worth keeping but clearly labelled as legacy. New systems should rely on DRM/KMS drivers with fbdev emulation, but the subsystem still serves a real purpose: efifb gives modern UEFI machines a working boot console, and a long tail of older workstation and embedded hardware has no DRM equivalent. Upstream maintainers (notably Thomas Zimmermann's 2023 series) are refactoring fbdev to make more of it optional rather than removing it outright, so it remains actively maintained in a hospice-care sense.

repository signals

433 files
264,452 source lines
1,131 commits, 5y
+14,133 / −32,860 lines added / removed, 5y
233 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 1,131 total · active in 58/61 months
2021 2022 2023 2024 2025 2026 2021-04: 3 commits · +5 −4 2021-05: 11 commits · +38 −45 2021-06: 4 commits · +44 −7 2021-07: 16 commits · +142 −70 2021-08: 3 commits · +28 −12 2021-09: 22 commits · +112 −759 2021-10: 8 commits · +56 −56 2021-11: 7 commits · +42 −19 2021-12: 14 commits · +70 −37 2022-01: 12 commits · +171 −70 2022-02: 27 commits · +971 −248 2022-03: 13 commits · +132 −47 2022-04: 46 commits · +765 −723 2022-05: 16 commits · +70 −94 2022-06: 33 commits · +122 −115 2022-07: 34 commits · +852 −1,008 2022-08: 19 commits · +275 −213 2022-09: 15 commits · +44 −1,884 2022-10: 16 commits · +50 −3,689 2022-11: 34 commits · +495 −556 2022-12: 22 commits · +145 −188 2023-01: 12 commits · +54 −75 2023-02: 10 commits · +146 −177 2023-03: 83 commits · +377 −527 2023-04: 28 commits · +360 −709 2023-05: 21 commits · +166 −112 2023-06: 44 commits · +965 −801 2023-07: 43 commits · +449 −765 2023-08: 68 commits · +285 −2,325 2023-09: 59 commits · +749 −687 2023-10: 12 commits · +42 −60 2023-11: 66 commits · +495 −445 2023-12: 14 commits · +200 −2,798 2024-01: 29 commits · +79 −5,274 2024-02: 10 commits · +39 −124 2024-03: 19 commits · +114 −116 2024-04: 14 commits · +76 −47 2024-05: 0 commits · +0 −0 2024-06: 17 commits · +28 −32 2024-07: 13 commits · +62 −48 2024-08: 8 commits · +60 −55 2024-09: 20 commits · +98 −93 2024-10: 10 commits · +130 −1,901 2024-11: 0 commits · +0 −0 2024-12: 4 commits · +22 −33 2025-01: 8 commits · +15 −23 2025-02: 8 commits · +144 −155 2025-03: 16 commits · +1,647 −2,354 2025-04: 9 commits · +59 −52 2025-05: 5 commits · +15 −7 2025-06: 18 commits · +140 −183 2025-07: 11 commits · +77 −88 2025-08: 7 commits · +136 −71 2025-09: 14 commits · +726 −681 2025-10: 12 commits · +118 −52 2025-11: 8 commits · +38 −45 2025-12: 7 commits · +23 −1,443 2026-01: 7 commits · +33 −21 2026-02: 14 commits · +562 −615 2026-03: 1 commit · +6 −2 2026-04: 0 commits · +0 −0

sources

  1. spinics.net

    Thomas Zimmermann's 2023 fbdev patch series says modern Linux distributions have adopted DRM for graphics output, fbdev is largely legacy, and future work is to make more fbdev userspace/file-I/O pieces optional rather than remove the subsystem outright.

  2. cateee.net

    Current LKDDb entry for CONFIG_FB shows fbdev is still present through current kernels/HEAD, and its help text explicitly says DRM provides emulated framebuffer devices on top of KMS while CONFIG_FB enables legacy native fbdev drivers.

  3. cateee.net

    EFI framebuffer support remains in current kernels, showing fbdev still covers a live firmware-framebuffer/boot-console niche on modern UEFI systems.

  4. cateee.net

    The directory still includes drivers for clearly legacy hardware such as DEC TGA/SFB+ boards, indicating a substantial long-tail preservation role rather than a subsystem centered on new mainstream products.

codex reasoning notes (technical)

Real driver subsystem, not an auxiliary directory: local shell inspection of drivers/video/fbdev/Kconfig shows many native framebuffer drivers and the FB menu. Upstream activity is clearly still present (given task metadata plus web-searched 2023 patch thread at spinics from turn2search2), but the thread frames fbdev as legacy and moving toward optional userspace exposure instead of immediate subsystem removal. Replacement path is explicit in local Kconfig and corroborated by LKDDb (turn3search0): DRM/KMS with fbdev emulation. Deployment is not zero because firmware framebuffers such as efifb are still relevant on new UEFI machines (turn3search3), while many native chip drivers are for old workstation/embedded hardware (turn3search1). Chosen keep-annotate: active maintenance/refactoring argues against deprecate/remove, but subsystem should be annotated as legacy with DRM preferred for new deployments.