VIOGPU(4)

πŸ“¦
version 11.0 Β· 2 versions
, in nixpkgs unstable

🌈 VIOGPU(4) β€” viogpu(4) from the Kernel Interfaces Manual 🌈

okay bestie, welcome to the manual page for viogpu(4) β€” yes, the manual name is right there, we’re doing this. It’s giving virtual-machine graphics but make it console, and I’m obsessed. πŸ’…


πŸŽ€ NAME πŸŽ€

viogpu β€” VirtIO GPU device ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

viogpu* at virtio?
wsdisplay* at viogpu?

that’s the whole synopsis, no cap. 🫢


πŸ’– DESCRIPTION πŸ’–

so the viogpu driver provides support for the virtio(4) GPU interface that QEMU and other virtual machines hand you, and its whole job here is to create a wscons(4) console. main character energy for your VM console, honestly. πŸ‘‘

but bestie, read the fine print: it does not provide access to the 3D functionality of the virtio GPU device. like, no 3D, periodt. 😭

and it also does not support mapping the framebuffer for generic graphics use by drivers such as wsfb(4). so don’t come for it with framebuffer-mapping expectations, okay? πŸ™ˆ


πŸ”₯ SEE ALSO πŸ”₯

go read those if you wanna be nosy, iykyk. πŸ“šβœ¨


🌸 HISTORY 🌸

the viogpu driver first appeared in OpenBSD 7.4, and it was ported for NetBSD 11. slay, cross-project moment. πŸŽ€πŸ’«


πŸ‘‘ AUTHORS πŸ‘‘

the viogpu driver was written by joshua stein <jcs@openbsd.org>. iconic behavior, fr fr. πŸ’œ


🫢 okay that’s the whole page! this one’s a Debian edition dated April 20 2023, filed under VIOGPU(4). bye bestie, drink water and don’t try to get 3D out of this driver! πŸ’–βœ¨
πŸ“¦ where this page comes from