>Because OpenGL is designed to go via the kernel rather than interface directly with the hardware, unlike directx.
this is pure nonsense
first: directx != direct3d
second: of course both apis "go via the kernel"!
and nobody had to spend much thought to "design" them that way, because what else would you expect? that's what a os kernel does, it multiplexes access to hardware! (which is why dos doesn't count as a real os btw)
>Vesa for example, a graphics driver, would though.
"vesa" is not a graphics driver
you don't know what you're saying
>By information, I'm only making a vague guess about ........
a gpu, even one that only advertises "direct3d capable" is not a "magical direct3d box"
a gpu is at its heart a collectionm of processors (mostly vector/superscalar/superpipelined architectures), some of them are fixed-function, some special-purpose, some general-purpose
a gpu driver will literally program those processors (the ones that are programmable anyway) in order to perform the intended "graphics processing", although it doesn't have to be "graphics"
these are not quite "direct3d" processors or "opengl" processors, they have their own architectures, isas, features, and limitations, much like a in a cpu
if the gpu vendor claims to support some particular api then it's natural for the hardware to be particularly well-suited to that api, but that does not mean one cannot use them to program and run other stuff (unless it's being artificially restricted, for example through firmware, because they have frmware, and can have nonvolatile memory, and of course can dma straight to your ass, plus gpu drivers are ridiculously complex, and humans don't know how to write secure programs... really, if you are running gigabytes of proprietary binary shit, aka vidya, just use windoos, you're hosed in either case)
anyway, every gpu driver (that i know about, and i'm talking about graphics accelerators , not random video/display hardware) will lower opengl/vulkan/direct3d/opencl/cuda/whathaveyou into so form of code+data to feed the gpu's processors
so what's gets "sent to the hardware" depends mostly on the driver, and what can actually be done with it depends on the hardware characteristics, the firmware, documentation... well, the same as a cpu