public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] linux: Do not enable dangerous legacy DRM drivers
Date: Wed, 03 Aug 2022 11:51:01 +0100	[thread overview]
Message-ID: <9CDE5CE1-4067-47B2-979B-9B44ACDA4270@ipfire.org> (raw)
In-Reply-To: <6ae4f7af-7c92-7b25-3c5f-2c959959c18d@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 2 Aug 2022, at 10:35, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> https://lists.ipfire.org/pipermail/development/2022-July/013886.html
> 
> This leaves current Nvidia Nouveau support untouched.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.x86_64-ipfire | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
> 
> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
> index 40975b5fc..3a05794aa 100644
> --- a/config/kernel/kernel.config.x86_64-ipfire
> +++ b/config/kernel/kernel.config.x86_64-ipfire
> @@ -5121,7 +5121,7 @@ CONFIG_DRM_AMD_DC_DCN=y
> 
> # CONFIG_HSA_AMD is not set
> CONFIG_DRM_NOUVEAU=m
> -CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=y
> +# CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set
> CONFIG_NOUVEAU_DEBUG=5
> CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> # CONFIG_NOUVEAU_DEBUG_MMU is not set
> @@ -5201,14 +5201,7 @@ CONFIG_DRM_XEN_FRONTEND=m
> CONFIG_DRM_VBOXVIDEO=m
> CONFIG_DRM_GUD=m
> CONFIG_DRM_HYPERV=m
> -CONFIG_DRM_LEGACY=y
> -# CONFIG_DRM_TDFX is not set
> -# CONFIG_DRM_R128 is not set
> -# CONFIG_DRM_I810 is not set
> -# CONFIG_DRM_MGA is not set
> -# CONFIG_DRM_SIS is not set
> -# CONFIG_DRM_VIA is not set
> -# CONFIG_DRM_SAVAGE is not set
> +# CONFIG_DRM_LEGACY is not set
> CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
> 
> #
> -- 
> 2.35.3


      reply	other threads:[~2022-08-03 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  9:35 Peter Müller
2022-08-03 10:51 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9CDE5CE1-4067-47B2-979B-9B44ACDA4270@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox