Quote Originally Posted by raster View Post
well it's not a wrapper. i would consider a wrapper something that intends to just hide the "nasty ugly raw details" of a lower level api and make it simpler. this is more than that. this glues in all of evas (canvas - scene graph) to render to kms/drm. not just wrap a raw frameuffer with swapping and mode setting, but to make the scene graph target this display device, so it's many layers up the tree (though we build everything ourselves on top of this higher level scene graph).
I thought it WAS addressing kms/drm directly. That this is intended to allow evas to run directly on the fb explains why my I confused. Yes, you can accelerate a tty/boot, and write a display server with it but none of those capture the actual target.
Thanks for the explanation. This makes much more sense and explains why you did it.