drivers/net/can/kvaser_pciefd

Kvaser PCIe and M.2 CAN/CAN FD interface cards

Kvaser's PCIe and M.2 add-in cards that bridge a PC to industrial CAN and CAN FD buses, used in automotive test rigs, factory automation, and embedded development. The product line includes single- and multi-channel PCIe boards (such as the PCIEcan 2xCAN v3) and M.2 modules (such as the 4xCAN), with hardware still being sold new in 2025.

keep conf=0.93 deploy=low replacement=none subsystem=net category=networking-other
93%

recommendation

It should stay in the kernel because Kvaser still sells current-generation PCIe and M.2 CAN FD boards in 2025 (such as the PCIEcan 2xCAN v3 and M.2 PCIe 4xCAN), and upstream development is visibly active: July 2025 linux-can patches reorganised the driver into its own directory and added devlink support. Older v2 boards are being retired, but newer variants in the same family keep arriving, so the driver serves a small but live industrial and embedded user base.

repository signals

4 files
2,064 source lines
6 commits, 5y
+2,073 / −6 lines added / removed, 5y
3 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 6 total · active in 2/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: 4 commits · +2,071 −4 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 2 commits · +2 −2 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. spinics.net

    July 2025 linux-can patch series restructured kvaser_pciefd into a dedicated directory/header split, indicating active upstream maintenance rather than retirement.

  2. spinics.net

    July 2025 net-next patch added devlink support for kvaser_pciefd, showing current feature work and review traffic.

  3. kvaser.com

    Kvaser was still selling PCIEcan 2xCAN v3 in 2025, a PCIe CAN/CAN FD board in this driver's product family, with explicit SocketCAN support.

  4. kvaser.com

    Kvaser was still selling M.2 PCIe 4xCAN hardware in 2025, showing new-deployment relevance for this PCIe CAN/CAN FD family.

  5. kvaser.com

    An older PCIe 2xHS v2 model is marked End of Life, suggesting generational churn inside the family but replacement by newer still-sold variants rather than driver obsolescence.

codex reasoning notes (technical)

Local shell inspection (`rg`, `sed`, `git -c safe.directory=... log`) confirmed this is a real PCI driver with 2025 feature commits and current PCI IDs including v2/v3/M.2-era devices. Web search located linux-can/netdev archive pages on spinics because the requested lore MCP server was unavailable and `lei` was not installed; those threads show active 2025 development, not removal talk. Web search also found current Kvaser product pages showing still-sold PCIe/M.2 CAN FD boards, while one older v2 page is EOL; overall this points to a live but niche industrial/embedded deployment base, so keep the driver.