Vetter: Why no 2D Userspace API in DRM?
Vetter: Why no 2D Userspace API in DRM?
Posted Aug 23, 2018 9:08 UTC (Thu) by Sesse (subscriber, #53779)In reply to: Vetter: Why no 2D Userspace API in DRM? by daniels
Parent article: Vetter: Why no 2D Userspace API in DRM?
In this understanding of “2D rendering” 3D engines can and do 2D rendering; your composited desktop (even without wobbly windows) is an example. Quads are rendered as two triangles—that's not a problem at all. But they're not suitable for extremely embedded platforms, since they use more area, gates and power than a pure 2D engine would do.
Posted Aug 23, 2018 14:17 UTC (Thu)
by nim-nim (subscriber, #34454)
[Link] (2 responses)
Text is the 2D rendering deal-breaker, unless you restrict yourself to ASCII-only single-size bitmap fonts, that do not work on hidpi screens, and that users loathe.
Even basic video players are increasingly expected to render nice non-pixelated i18n subtitles.
Posted Aug 23, 2018 15:28 UTC (Thu)
by louai (guest, #58033)
[Link]
1) Rendering individual glyphs (usually cached)
Either one of those can be accelerated, but generally speaking you get a lot more bang for your buck by making the second step fast. And that second step is really just blitting to screen.
Posted Aug 23, 2018 18:27 UTC (Thu)
by Sesse (subscriber, #53779)
[Link]
They still need to be blit to screen one by one, but then we're back to the “get a rectangle from A to B” land.
Vetter: Why no 2D Userspace API in DRM?
Vetter: Why no 2D Userspace API in DRM?
2) Putting these glyphs on screen
Vetter: Why no 2D Userspace API in DRM?