A GPU with HDMI and 16MB of VRAM is a very strange combination.
For dual-monitor versions?
One avenue I looked at for a real 2560px width was that the second controller was physically independent and could have different hardware limits of the first controller by virtue of supporting DVI directly (but not being physically connected to another port).
Unfortunately other controller is logical so that was a bust.
On the same machine I experimented with IOMMU and a lightweight VM to run Nvidia Pascal era GPUs in a VM with 580 drivers, while Nvidia Blackwell on the host uses 590. I vibe coded that too
When exposed via openai compatible endpoints with GPUStack https://github.com/gpustack/gpustack I could use the combined compute power from both generations on a single machine.
VGA displays are something of a dying breed, and HDMI is the single likeliest interface you might find on a random newish display, so there is a market for absolute cheapest, most basic HDMI output device you can make. If you're going to build that interface, 1080p is the resolution you need to target. My point was simply that 16MB is just barely enough to build that interface, and barely enough is still enough.
Some switches have already started using USB-C for serial instead of RJ45. When the technician is 100% already carrying a smartphone and C-to-C cable to charge it, making the console available with zero additional adapters is quite attractive.
You can put a USB to RS232C or USB to Ethernet adapter behind the port to then expose ttyS0 or to serve a management webpage, that could happen, but I think the DB-9 and/or RGB would have to stay in that case.
^ / 1024^2[bytes/MB] = 23.73[MB]