LVC21F-108 Advanced KMS: virtualized planes as a way to hide hardware implementation details

Session Abstract

Typically a DRM KMS driver will expose hardware blocks by registering objects: planes, crtcs, encoders corresponding to those blocks, allowing userspace to precisely select what it can do. In some cases it makes sense to register objects which are not directly mapped to hardware resources and let the driver select hardware resources backing these objects on its own.

Session Speakers

Dmitry Baryshkov

Linaro - driving open source development on ARM (Linaro Ltd)

Dmitry has been working in embedded Linux area since 2006. Since 2007 he has been working in the development services area (at Siemens and Mentor Graphics). In 2015-2019 Dmitry has been working at Cavium Inc, improving system software for ThunderX and OcteonTX. For two years Dmitry was Cavium's assigned engineer at Linaro. In 2020 he has joined Linaro again, now being part of Developer services team.

Typically a DRM KMS driver will expose hardware blocks by registering objects: planes, crtcs, encoders corresponding to those blocks, allowing userspace to precisely select what it can do. In some cases it makes sense to register objects which are not directly mapped to hardware resources and let the driver select hardware resources backing these objects on its own.

comments powered by Disqus

Recent Posts

Other Posts

Sign up. Receive Updates. Stay informed.

Sign up to our mailing list to receive updates on the latest Linaro Connect news!