Description
The Graphics & DRM Microconference welcomes the community to discuss topics around the Linux graphics stack and the DRM subsystem, with the goal of solving long standing and complex problems together.
The MC CfP is open to all proposals related to graphics, including the following potential topics:
- Rust and DRM
- Color management and HDR
- Automated tests of GPUs and the stack
- cgroups support
- Device reset management
- DRM and IA accelerators
MC Leads:
- André Almeida
- Daniel Stone
-
André Almeida (Igalia)18/09/2024, 15:00
-
Helen Koike (Collabora), Sebastian Fricke18/09/2024, 15:05
Everybody seemingly needs CI and a lot of subsystems already have their spin of
CI running, but everyone is cooking their soup, while when we look at it
the majority of what the CI systems do is very, very similar.This proposal aims to highlight the different attempts currently floating
Go to contribution page
around (DRM CI, MediaCI, KCI-Gitlab, CKI, Intel XE, etc.), depicting the
large overlaps but also the... -
Dmitry Baryshkov (Linaro Ltd.)18/09/2024, 15:30
While MIPI DSI bus and MIPI devices has been supported in Linux kernel for quite a while, during the last few years several important corner cases were identified, which make it hard to fit the MIPI DSI devices into the standard DRM pre-enable / enable / disable / post-disable model. Some of the shortcomings were solved via the pre_enable_prev_first call, other shortcomings remain unsolvd....
Go to contribution page -
Luca Ceresoli (Bootlin)18/09/2024, 16:00
Traditional DRM pipelines for embedded devices have no removable components, while PC-style pipelines have long time supported hotplug of the panel only, via standardized connectors such as HDMI or DisplayPort.
Embedded devices being currently developed by the industry have a video pipeline whose last components, including one or more bridges, are located on a hot-pluggable add-on using a...
Go to contribution page -
André Almeida (Igalia)18/09/2024, 17:00
GPU resets are a common problem for every vendor, due to the nature of the stack. A bad shader can put the render node in an infinite loop, and we need to reset the GPU, partially or completely. However, each driver (both at userspace and kernelspace) have different ideas of what to do when a reset happens.
The goal of this session is to try to find a better common ground of how to manage...
Go to contribution page -
Prakash Gupta (Qualcomm)18/09/2024, 17:30
Kernel supports default cma and system dmabuf heaps. In order to support protected usecase, additional heap types needs to be supported.
There are quite a few downstream dmabuf heaps maintained by vendors to support protected usecase. There is need to provide generic framework, which will reduce fragmentation of such dmabuf heap types.
The proposed restricted dmabuf heaps will support...
Go to contribution page -
18/09/2024, 18:00
This is a open slot that can be used if the MC contributors wants more time to work together in some topic
Go to contribution page
