Digi International Neo and Classic PCI multiport serial adapters
A family of 32-bit PCI add-in cards from Digi International that fanned a single PCI slot out into multiple RS-232 serial ports, used from the late 1990s and 2000s in server rooms and industrial settings to drive banks of modems, terminals, point-of-sale gear, and console connections. Digi has since marked these Neo and Classicboard products obsolete.
recommendation
Worth keeping but flagging as legacy hardware. The cards are no longer sold and Digi's own support pages list them as obsolete, so deployments today are likely small and shrinking, but the code is still being maintained in tree, with a real bug fix landing in stable in late 2022 and a treewide PCI cleanup touching it in October 2025. Nobody is currently proposing removal, so leave it in place and document its niche status rather than deprecating it.
repository signals
sources
- lore.kernel.org
The driver still received a real bug-fix in stable trees in October 2022 ('drivers: serial: jsm: fix some leaks in probe').
- lore.kernel.org
The driver was still touched by a treewide PCI API cleanup in October 2025, indicating it is not abandoned in-tree.
- cateee.net
LKDDb identifies CONFIG_SERIAL_JSM as support for Digi International Neo and Classic PCI boards and lists the supported PCI device IDs.
- digi.com
Digi labels its PCI serial adapter knowledge-base article as covering an 'obsolete product' and describes these adapters as 32-bit PCI cards.
- digi.com
Digi's Linux installation article for Neo and Classicboard PCI adapters is also explicitly marked as an 'obsolete product'.
codex reasoning notes (technical)
Source acquisition: lore_file_timeline/lore_activity MCP yielded the 2022 stable bug-fix URL and 2025 treewide PCI cleanup URL; web search yielded LKDDb and Digi knowledge-base pages. The code and LKDDb identify old Digi Neo/Classic PCI multiport serial cards. Digi's own support pages mark the product line obsolete, so new 2025 sales are unlikely; however, lore still shows occasional maintenance and stable carry, with no removal discussion surfaced in the lore timeline. That argues against deprecate/remove today; keep the driver, but annotate it as legacy/obsolete hardware with likely low present-day deployments.