Linux 7.4-rc2 Brings HDMI 2.2 FRL Support, Massive FAT32 Speedup, and Faster Builds
Developers submitted fixes for Linux 7.4 that enable the AMDGPU graphics driver to recognize HDMI 2.2 Fixed Rate Link (FRL) speeds, addressing a limit that could keep compatible displays below their supported link rate. The patches were headed for Linux 7.4-rc2, expected Sunday. Other changes in the release candidate include a FAT32 file-expansion optimization that avoids repeated small cluster allocations, along with sound-driver fixes and device-specific workarounds. In build tests, Linux 7.4-rc1 compiled about 5% faster than Linux 7.3 with a default x86-64 configuration, but slightly slower when building all kernel modules. In QEMU benchmarks, the new FAT32 expansion optimization delivered speedups of up to 162 times, particularly on synchronous mounts with small cluster sizes. Sound updates add support for several HP systems using AMD ACP 7.0 and address microphone capture, headset detection, mute indicators and audio noise across HP, Huawei, Acer, Lenovo and ASUS devices. Linux 7.4 also includes patches to speed up incremental and no-op builds; the full patch series can bring build times close to 10 seconds with enough CPU cores.
Look closely at the patch set heading into Linux 7.4-rc2. The mainstream will tell you it is a simple driver fix—enabling the AMDGPU to recognize HDMI 2.2 Fixed Rate Link speeds. They want you to see an optimization. I see an admission. Why was that limit there in the first place? The HDMI Forum is a closed consortium of the same display manufacturers and content cartels who dictate your upgrade cycles. That "cap" wasn't a bug. It was a contractual handbrake, a piece of digital friction applied to the entire open-source ecosystem to ensure that display standards remain a managed bottleneck. The fact that it is now being "fixed" in the kernel tells me the architecture of control is shifting from the hardware spec itself to the software stack above it. They didn't remove the limit because they were being generous. They removed it because they were forced to, because the next layer of the cage is already in place.
But the real smoking gun in this release candidate is buried in the filesystem layer. The FAT32 "expansion optimization." Let that sink in. A 162x speedup on synchronous mounts. Read that number again. One hundred and sixty-two times. How is that possible unless the previous implementation was deliberately crippled? FAT32 is the universal language of removable media—the USB drive, the SD card, the firmware update. It is the de facto standard for moving data outside of the cloud surveillance panopticon. For years, this code path was performing small cluster allocations so inefficiently that it created a user-experience tax on anyone trying to use offline storage. Was it really an oversight? Or did the legacy code base serve a very specific function: making the cloud the only viable path for modern workflows? Every second of lag on a FAT32 drive is a nudge towards Google Drive, OneDrive, and iCloud—where every packet is logged. This "fix" isn't a performance patch; it is a lock being cracked open by a front-door apology.
Now watch the third leg of this stool. The build system itself is being optimized—a 5% compile speedup, and the claim that full builds can approach ten seconds. Why the sudden urgency to accelerate the development cycle? Because the people who submitted these patches know the clock is ticking. They are cleaning up the obvious tells. The sound driver fixes for "Huawei, Lenovo, HP, Acer"—why that specific list? Why those precise hardware IDs in the same patch cycle as the display limit concession and the storage speed unlock? You don't need to guess. The documents are public. The commit log is the new JFK files. The question isn't what was broken. The question is who ordered it broken in the first place, and who is now ordering it fixed. I have told you for years that the war for your digital sovereignty is fought in the invisible layers of code. Here is the proof. Don't just read the release notes. Look at the history. Follow the footprints. They are running.
