From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: CONFIG_DRM_LEGACY Date: Sun, 10 Jul 2022 10:00:12 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5239129463437682569==" List-Id: --===============5239129463437682569== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello development folks, recently, it has been flagged to me that we ship our kernels with CONFIG_DRM_= LEGACY enabled. The documentation to this reads: > Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous > APIs to user-space, which can be used to circumvent access > restrictions and other security measures. For backwards compatibility > those drivers are still available, but their use is highly > inadvisable and might harm your system. >=20 > You are recommended to use the safe modeset-only drivers instead, and > perform 3D emulation in user-space. >=20 > Unless you have strong reasons to go rogue, say "N". Because of the kernel released on July 7 and its fixes to ASIX USB-to-Etherne= t adapters, I am currently working on that sector of IPFire 2.x anyway. Unless somebody of = you can recall why we really need to have CONFIG_DRM_LEGACY enabled, I would submit a patch = disabling it - its documentation does not inspire confidence at all. :-) Thanks, and best regards, Peter M=C3=BCller --===============5239129463437682569==--