Ah you mean this https://www.pcworld.com/article/393815/the-asrock-rack-m2-vg...

That one is VGA so I think the original upstream driver should support it.

To be fair, vibe coding is only possible because the models have been trained on the countless open source projects out there. And it could take the original drivers as basis in Linux.

I guess this is trolling, but I've never claimed credit for the traditional coding part.

The unique bits I did do

- Checked the specs for actual hardware limits, DMA and any acceleration

- A magic dither based on my previous (normally coded) older projects (see GitHub)

- Image width "compression" idea with loss reduction using sharpening and a slight aspect change.

- Optimising DMA size chunking for optimal memory transfer.

- A lot of actual manual testing, including sheer reduction, frame rate testing, and multiple resolution and different monitor tests (and I lost one - the HDMI port no longer works on my old Celcus)

Failed experiments with:

- using the onboard secondary controller to bypass the primary controller limitations

- devising a hack that would use the vertical scan horizontally using monitor rotation

- attempting an 8, not 16/32 bit desktop for higher performance (old school technique).

- investigating non hardware hacks for overclocking the onboard chips.

- fixing a KVM issue, that required multiple physical disconnects and reconnects to replicate, and a significant amount of weekend time.

So yeah, vibe coded, because I'd never have been able to try these ideas in such a short timescale if I hadn't.

Don't you people have something better to do than hound people for their choice of tools?

That's a thing that happens, but this doesn't look like that.

The words "I vibe coded this" explicitly disclaim any excess credit.

They did exactly what anyone can reasonably ask for. They exhibited essentially perfect integrity.

I'm assuming your gotcha is going to be "but that's not vibe-coding", but in case you're sincere, you might not have realised this yet: there's a whole range between writing every line by yourself and letting the slop machine create the entire thing. You can rely on your knowledge and understanding to guide it, to the point that it writes code that you would have written, but saves you an enormous amount of time and effort looking up things and creating/running small tests to figure out details. It's a tool, not a spell, so your pearl clutching is a few years out of date...