drivers/gpib/fmh_gpib

FMH GPIB FPGA controller core

An open-source GPIB (IEEE-488) controller written in VHDL by Frank Mori Hess and synthesized into an FPGA, used by labs to talk to legacy test-and-measurement instruments like oscilloscopes and signal generators. It is a soft core that engineers load onto their own FPGA hardware, typically described to Linux through device tree.

keep-annotate conf=0.83 deploy=low replacement=none subsystem=gpib category=bus-other
83%

recommendation

Worth keeping but documenting its narrow niche. The hardware is a VHDL GPIB controller core that lab users program into an FPGA rather than a retail card you can buy, and enumeration relies on device tree or placeholder PCI IDs. Even so, it was promoted out of staging into drivers/gpib in late 2025 and received further fixes in early 2026, so it has an active, if small, user base of FPGA-equipped instrumentation labs.

repository signals

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

sources

  1. linux-gpib.sourceforge.io

    Describes fmh_gpib_core as a GPIB chip written in VHDL for programming into an FPGA, with deployment via device-tree-defined FPGA resources rather than a mainstream retail board.

  2. cateee.net

    Shows CONFIG_GPIB_FMH in mainline kernels after staging, and lists only the OF compatible "fmhess,fmh_gpib_core" plus bogus PCI IDs ffff:0000, indicating niche/nonstandard hardware enumeration.

  3. codebrowser.dev

    Confirms the driver targets fmh_gpib_core, matches OF compatible "fmhess,fmh_gpib_core", and uses bogus Fluke PCI IDs rather than normal production IDs.

codex reasoning notes (technical)

This is a real driver directory. Local shell inspection of fmh_gpib.c confirmed module_init/module_exit and platform+PCI registration. Local `git -c safe.directory=... log --follow -- drivers/gpib/fmh_gpib` showed the driver was destaged into drivers/gpib on 2025-11-17 and received two non-mechanical fixes on 2026-01-16, which argues against deprecation/removal despite low commit volume. I could not get lore MCP access in this session, so upstream-attention evidence came from local git history instead. URL evidence was obtained by web search: `turn0search0`/`turn2search0` for the linux-gpib supported-hardware page, `turn0search2`/`turn2search2` for LKDDb, and `turn2search1` for codebrowser. Conclusion: extremely niche FPGA-based GPIB hardware, likely low deployment and not a mainstream new-sale product in 2025, but recently promoted from staging and still seeing fixes; keep it, with annotation that it serves a narrow legacy/lab FPGA niche.