mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sui Jingfeng <suijingfeng@loongson.cn>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Mips: loongson3_defconfig: Enable ast drm driver by default
Date: Tue, 15 Aug 2023 10:29:27 +0200	[thread overview]
Message-ID: <ZNs3ZwYH5N/uumJP@alpha.franken.de> (raw)
In-Reply-To: <20230803091637.971924-1-suijingfeng@loongson.cn>

On Thu, Aug 03, 2023 at 05:16:37PM +0800, Sui Jingfeng wrote:
> ASpeed GPU is typically found on the Loongson server platform, as a
> peripheral device driver, it generally should be compiled as a module.
> 
> Tested on loongson 3B4000 server[1].
> 
> [1] https://github.com/loongson-gfx/loongson_boards/tree/main/ls3b4000x2_server
> 
> Signed-off-by: Sui Jingfeng <suijingfeng@loongson.cn>
> ---
>  arch/mips/configs/loongson3_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/mips/configs/loongson3_defconfig b/arch/mips/configs/loongson3_defconfig
> index 3087e64e6ebe..a9fadea72da5 100644
> --- a/arch/mips/configs/loongson3_defconfig
> +++ b/arch/mips/configs/loongson3_defconfig
> @@ -283,6 +283,7 @@ CONFIG_DRM_AMDGPU_USERPTR=y
>  CONFIG_DRM_AMD_ACP=y
>  CONFIG_DRM_AMD_DC=y
>  CONFIG_DRM_AMD_DC_SI=y
> +CONFIG_DRM_AST=m
>  CONFIG_DRM_RADEON=m
>  CONFIG_DRM_QXL=y
>  CONFIG_DRM_VIRTIO_GPU=y
> -- 
> 2.34.1
> 

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-08-15  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  9:16 Sui Jingfeng
2023-08-15  8:29 ` Thomas Bogendoerfer [this message]
2023-08-15  9:21   ` suijingfeng

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=ZNs3ZwYH5N/uumJP@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=suijingfeng@loongson.cn \
    /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

all inboxes | Powered by JetHome®