Bug 1986223 - [RFE] Please turn on SimpleDRM driver
Summary: [RFE] Please turn on SimpleDRM driver
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Jocelyn Falempe
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-27 01:05 UTC by Neal Gompa
Modified: 2023-08-09 19:19 UTC (History)
32 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1986222
Environment:
Last Closed: 2023-07-30 07:27:57 UTC
Type: Enhancement
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Neal Gompa 2021-07-27 01:05:36 UTC
+++ This bug was initially created as a clone of Bug #1986222 +++

Description of problem:
Linux 5.14 introduces the new SimpleDRM driver as a generic fallback driver that supports KMS. GNOME Wayland does not support non-KMS graphics for rendering, and KDE Plasma's non-KMS (fbdev) rendering mode pretty much does not work. This driver makes it possible for desktop environments to *always* expect KMS to work, even if a native driver isn't available, which makes it simpler to support Wayland.

Please enable SimpleDRM so that it becomes achievable to use Wayland for "basic graphics mode" fallback configurations.

Version-Release number of selected component (if applicable):
5.14.0-0.rc3.29.el9

Additional info:
The lack of this driver led to bug 1952431 happening during Fedora Linux 34's development and I would really like SimpleDRM to be enabled so I can make more progress on solidifying Wayland support and remove hacks to disable Wayland in "basic graphics mode".

Comment 3 Javier Martinez Canillas 2021-12-24 13:03:09 UTC
I've proposed the following merge request to kernel-ark:

https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1533

Comment 9 RHEL Program Management 2023-01-27 07:27:55 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 10 Niels De Graef 2023-01-30 10:18:39 UTC
Re-opening since this is just our stale bot being too eager

Comment 13 RHEL Program Management 2023-07-30 07:27:57 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 14 Niels De Graef 2023-08-09 09:35:40 UTC
Again, please don't mind our overeager stale bot at times.

Comment 16 Neal Gompa 2023-08-09 13:08:57 UTC
:)


Note You need to log in before you can comment on or make changes to this bug.