Barco has long supplied specialized graphics cards for high-stakes medical imaging. Hospitals and radiology departments rely on them to drive multiple diagnostic displays with pixel-perfect accuracy. Until this week those cards ran only on Windows.
A quiet kernel patch changes that.
Matthew Jacob, a developer at Feral Software, submitted code that adds several Barco device identifiers to the AMDGPU Linux driver. The change landed on the amd-gfx mailing list June 19, 2026. It requires no new functions. No altered rendering paths. Just PCI IDs mapped to existing silicon families already well supported in the kernel. Simple. Effective.
The patch covers four models. MXRT-5600 sits on Bonaire silicon. MXRT-7600 uses Tonga. Two Polaris-based entries appear as tentative MXRT-8750 and MXRT-4700. The latter already exists in Barco’s catalog; the 8750 has not yet reached public release. Phoronix first reported the submission.
Jacob offered a concise rationale in the commit message. “These adapters typically are only supported by Barco on the Windows platform. However, with these changes in the linux driver, multiple monitor support should work correctly.” That single sentence captures years of market reality. Barco publishes full driver packages exclusively for Windows. Its support matrix and knowledge-base articles explicitly state that Linux configurations remain untested and unsupported. Diagnostic software such as QAWeb and the associated calibration tools exist only for Microsoft platforms.
Yet the underlying GPUs come from AMD’s professional Radeon Pro lineage. Bonaire, Tonga, and Polaris chips have shipped in countless Linux workstations for more than a decade. Their display engines, memory controllers, and multi-monitor capabilities sit inside the AMDGPU driver today. Barco simply never asked the community to expose the vendor-specific IDs. Until now.
The timing feels telling. Linux adoption inside hospital IT departments has accelerated. Research labs run Ubuntu or Rocky Linux for AI-assisted diagnostics. PACS servers increasingly standardize on open-source stacks. Even radiology reading rooms experiment with Linux thin clients to cut licensing costs. Without driver support those Barco cards sat idle or required awkward dual-boot setups. This patch removes one technical barrier.
Don’t mistake it for full certification. Barco has issued no statement. No QAWeb package runs natively on Linux. Calibration routines and DICOM compliance checks still demand Windows. The patch merely lets the kernel recognize the hardware and light up the outputs. Multiple 10-bit 4K displays should initialize. Color management will depend on userspace tools already present in Mesa and the AMDGPU stack. Basic functionality arrives. Enterprise validation remains distant.
Still, the move carries practical weight. Enthusiasts have long known that many MXRT cards share hardware with FirePro or Radeon Pro equivalents. Some users flash alternative BIOS images to unlock standard drivers. Jacob’s patch makes that unnecessary. It brings the cards into the mainline driver without custom firmware or out-of-tree modules. Future kernel releases will carry the IDs by default once merged.
AMD itself has deepened its medical imaging ties over the years. A 2011 partnership announcement highlighted joint work on enhanced visual imaging for diagnosis. Barco chose AMD GPUs for the original MXRT series because of their stability under 24/7 loads and strong multi-display output. That relationship continues. Recent Barco announcements focus on newer MXRV models built on NVIDIA silicon, yet the AMD-based MXRT line persists for customers who prefer that ecosystem.
Industry observers note the patch arrives against a backdrop of broader AMD Linux momentum. Recent kernels improved recovery for early GCN parts. Radeon Software for Linux sees regular updates. Open-source graphics drivers now power everything from supercomputers to developer desktops. Adding a handful of medical-oriented PCI IDs fits neatly into that pattern. It costs AMD and the kernel maintainers almost nothing. It delivers immediate value to a narrow but demanding user group.
Practical implications stretch beyond radiology.
Any Linux workstation tasked with driving four or six high-resolution panels stands to benefit. Scientific visualization labs. Flight simulators. Command-and-control centers. All share the same requirement for rock-solid multi-monitor output. The MXRT cards, with their medical-grade firmware and long availability commitments, suddenly become viable in those environments. Pricing on the secondary market may shift once Linux compatibility becomes common knowledge. One X user already speculated that “say goodbye to stupid-cheap deals on those cards.”
Barco’s own documentation still directs customers to its support portal for Windows-only downloads. The April 2026 knowledge-base article walks users through locating the latest MXRT or MXRV packages. No Linux section exists. That gap will likely persist until the company decides to invest in validation. In the meantime the open-source community has done the minimal work required to make the hardware functional.
The patch itself reads like many others that have expanded AMDGPU coverage. A few lines in a table. New entries in the device list. Comments that tie each ID back to its Barco marketing name. Reviewers on the mailing list will likely accept it without controversy. The code touches only identification logic. Risk remains low.
So Linux users in medical imaging finally get official recognition for hardware they may have owned for years. The change won’t transform hospital procurement overnight. It does, however, remove an artificial limitation that never stemmed from technical impossibility. The silicon was always capable. The driver simply needed to know the names.
And now it does.
WebProNews is an iEntry Publication