[PATCH 14/14] drm: Remove Kconfig option for legacy support (CONFIG_DRM_LEGACY)
Alex Deucher
alexdeucher at gmail.com
Mon Nov 27 21:07:27 UTC 2023
On Wed, Nov 22, 2023 at 7:25 AM Thomas Zimmermann <tzimmermann at suse.de> wrote:
>
> Remove CONFIG_DRM_LEGACY from Kconfig. Nothing depends on the option.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
Acked-by: Alex Deucher <alexander.deucher at amd.com>
> ---
> drivers/gpu/drm/Kconfig | 21 ---------------------
> 1 file changed, 21 deletions(-)
>
> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> index cdbc56e076498..5150c8699a8b5 100644
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
> @@ -407,27 +407,6 @@ config DRM_HYPERV
>
> If M is selected the module will be called hyperv_drm.
>
> -# Keep legacy drivers last
> -
> -menuconfig DRM_LEGACY
> - bool "Enable legacy drivers (DANGEROUS)"
> - depends on DRM && MMU
> - help
> - 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.
> -
> - You are recommended to use the safe modeset-only drivers instead, and
> - perform 3D emulation in user-space.
> -
> - Unless you have strong reasons to go rogue, say "N".
> -
> -if DRM_LEGACY
> -# leave here to list legacy drivers
> -endif # DRM_LEGACY
> -
> config DRM_EXPORT_FOR_TESTS
> bool
>
> --
> 2.42.1
>
More information about the dri-devel
mailing list