Linux 7.2 is set to remove a driver for a piece of hardware that is roughly 35 years old, but that change does not mean support for the device is disappearing. The code being retired is dtlk, the dedicated driver for the RC Systems DoubleTalk PC ISA speech synthesizer card, an accessibility device released in 1991.
The important detail for users is that the same hardware can still work through another path in Linux. Support remains available through drivers/accessibility/speakup for screen reader use, so the removal affects one standalone code path rather than the card’s overall compatibility with the kernel.
This kind of cleanup reflects how Linux handles very old hardware. The kernel has long carried support for obscure devices, but every line of code also has to be maintained, reviewed, and adjusted as the rest of the system evolves.
In this case, the driver was not removed because the hardware no longer mattered. The problem was the driver itself, which was described as having serious code-style issues and very little development history behind it.
The patch notes indicate that dtlk had only seen broad tree-wide cleanup and minor fixes since Linux 2.6. Beyond that, there was little sign of active maintenance, which made the driver a candidate for removal.
Another factor was that the implementation in speakup does not share code with dtlk. That means the standalone driver was not providing a unique technical foundation for the device’s support.
There was also an assumption that the driver may no longer be used at all. When a rarely touched driver brings maintenance cost without clear benefit, removing it becomes easier to justify.
DoubleTalk PC ISA itself is notable because it is not ordinary legacy hardware. It is a speech synthesizer card built for accessibility, and its survival in Linux shows how far kernel compatibility can stretch across generations of computers.
At the same time, the change shows that long support histories still have practical limits. Linux can preserve old-device support without keeping every aging driver forever, especially when another maintained path already covers the same hardware.
For that reason, the removal of dtlk should be read as maintenance work rather than a shutdown of support. The kernel is dropping one problematic driver while keeping access to the device through a different accessibility subsystem.
Source: www.xda-developers.com