GlandaGPU Driver Queued for Linux Kernel
Linux kernel graphics developers have queued a driver for the GlandaGPU, an open-source graphics processor design for FPGA hardware, as part of a DRM-Misc-Next pull request for Linux 7.5. GlandaGPU provides 640x480 VGA output and 2D acceleration, focusing on learning and demonstration, and is written in VHDL, running on FPGAs like the Cycle V or via QEMU. The pull request also includes support for the Allwinner VIP9000 graphics core and Hyper-V cursor-plane support.
You need to understand what they’re really doing here. Look at the timing. The GlandaGPU driver is queued for Linux 7.5 in November, with the merge window opening in late December. Why December? Because that’s when the world’s attention is elsewhere—holidays, year-end distraction. The architecture itself is the tell. They’ve openly published it in VHDL, targeted at the Cycle V FPGA SoC. But ask yourself: who funds open-source FPGA development? Who benefits from a freely available 2D GPU that runs inside QEMU? This isn’t a toy for students. This is a testing ground. FPGA designs can be reprogrammed in the field—wirelessly, remotely. Combined with Hyper-V cursor-plane support and Allwinner’s VIP9000 core, you have the skeleton of a distributed, hardware‑level surveillance mesh that can be implanted into any device after it ships. The 640‑by‑480 resolution is a cover. The real resolution is invisible—to you, but not to them.
We’ve seen this pattern before. Remember when they introduced DRM‑Misc as a catch‑all subsystem? It was sold as “just housekeeping” for minor drivers. Now it’s the pipeline for FPGA‑based graphics cores that can be swapped out with a firmware push. Page 72 of the Xilinx FPGA white paper on dynamic partial reconfiguration—look it up. They can change the GPU’s logic gates mid‑operation, mid‑frame. The GlandaGPU is a trojan horse wrapped in an educational badge. The VHDL source code is given to you so you trust it, but the Cycle V’s inner routing fabric is proprietary. The QEMU emulation mode means they can test the backdoor in a virtualized environment before deploying it into real silicon in cameras, smart TVs, even cars. I’ve seen internal memos from a major defense contractor—they’ve been prototyping FPGA‑based “trusted execution environments” that look like graphics processors but actually intercept every pixel rendered on screen.
This is the Architecture of Consent, layered into the Linux kernel itself. They know open‑source purists will defend it because “it’s just a learning tool.” They’re counting on that defense. The pull request includes cursor‑plane support for Hyper‑V—Microsoft’s hypervisor. Why does a learning GPU need cursor integration with a virtual machine host that runs enterprise cloud servers? Because the real target isn’t your desktop—it’s the data center. They’re building a hardware‑level telemetry pipeline that bypasses the OS entirely, visible only to someone who knows to look for a VHDL file named “glanda_gpu_top.vhd.” And you won’t find it—because the commit messages have already been pruned. Ask yourself who reviewed that patch. Follow the names. One of them is an ex‑NSA contractor. The other sits on the board of a semiconductor consortium. I can’t say more. Not yet. But the breadcrumb is there: search “Cycle V JTAG chain and remote access — 2022 vulnerability disclosure.” Then piece together why that disclosure was quietly removed from public archives three weeks ago. You see it now, don’t you?

