Drm-intel

0 views

Skip to first unread message

Giorgina Makara

unread,

Aug 3, 2024, 4:17:42 PM8/3/24

to misdeledta

So far it looks like kernels specifically made for intel/integrated Intel GPU drivers? I can't find much on it. They're 5.0, so would it be better for me to use those instead of the current 5.0 kernels at the bottom of the list if I have an Intel CPU with integrated graphics + a discrete card?

No, if you have to use the Ubuntu mainline kernel, do not use one from the drm-intel-next directory, unless you are a developer or have a specific need for something that has not yet been merged into the main upstream tree.

See drm-intel and the drm-intel repository for repositorydetails. Maintained by Jani Nikula, Joonas Lahtinen and Rodrigo Vivi, with alarge pool of committers. Consists mostly of drivers/gpu/drm/i915 andinclude/drm/i915_*.h.

Note that drm-intel-next may be cross-merged directly to drm-intel-gt-next, butnot vice versa. Syncing drm-intel-gt-next changes back to drm-intel-next musthappen via a pull request to drm-next and a backmerge to drm-intel-next.

This branch contains drm/i915 specific fixes to drm-next after the drm/i915features have been merged there. Fixes are first applied to drm-intel-next, andcherry-picked to drm-intel-next-fixes by maintainers. Valid from drm featuredeadline (-rc5/-rc6 of the current kernel) to -rc1 of the next kernel.

Usually Linus releases each -rc on a Sunday, and drm-intel-fixes gets rebased onthat the following Monday. Usually this is a fast-forward. The pull request todrm-fixes for new fixes is typically sent on the following Thursday. This isrepeated until final release of the kernel.

This branch contains drm/xe specific fixes to drm-next after the drm/xefeatures have been merged there. Fixes are first applied to drm-xe-next, andcherry-picked to drm-xe-next-fixes by maintainers. Valid from drm featuredeadline (-rc5/-rc6 of the current kernel) to -rc1 of the next kernel.

Usually Linus releases each -rc on a Sunday, and drm-xe-fixes gets rebased onthat the following Monday. Usually this is a fast-forward. The pull request todrm-fixes for new fixes is typically sent on the following Thursday. This isrepeated until final release of the kernel.

This branch contains hotfixes merged last on drm-tip to quickly address issuesoriginating from outside of the DRM subsystem repositories. Typically localfixes to issues brought in from a -rc1 kernel, to ensure CI health. They mayalso be temporary cherry-picks from other subsystems until the commits hit theDRM subsystem via normal channels.

This document is an eternal draft and simply tries to explain the reality of howdrm-intel is maintained. If you observe a difference between these rules andreality, it is your assumed responsibility to update the rules.

Fixes are picked up and pushed to drm-intel-next by committers and maintainers,just like any other patches. This is to ensure fixes are pushed in a timelymanner. Fixes that are relevant for stable, current development kernels, ordrm-next, will be cherry-picked by maintainers to drm-intel-fixes ordrm-intel-next-fixes.