@marcan well.. Nvidia still has native 2D acceleration commands 🙃 But I think it's the only vendor having that.
It also didn't change for 10 years. So maybe it gets deleted at some point.
Top-level
@marcan well.. Nvidia still has native 2D acceleration commands 🙃 But I think it's the only vendor having that. It also didn't change for 10 years. So maybe it gets deleted at some point. 5 comments
@marcan yeah.. though I kinda see their point using the 2D stuff to do large buffer copies instead of running a shader just copying bytes :D I have no idea if they actually have a 2D block or if it's emulated in shaders on the hardware. Anyway, the advantage is: implementing a driver is simpler (and has less CPU overhead). And I wouldn't be surprised it's the reason they kept it as it's still useful within writing a Vulkan (or whatever API) driver. @karolherbst Apple has a blitter too, but that isn't really a 2D engine (it's meant more for copies and mipmapping). Though they still use just shaders copying bits in some cases I think. @karolherbst @marcan On the ARM SoC side of things, Rockchip likes to throw blitters into everything. Multiple. There's not just the full blitter blocks with gradient fill functions, pixel format conversions, scaling, compositing, and rotating, of which there are sometimes several per SoC, but your video output block can scale and composite too, and your video decoder can scale as well. These are all in the same SoC (RK3588), in addition to a full Mali GPU. |
@karolherbst Ah, but who says I consider Nvidia hardware "modern"? 🙃