From: Sui JIngfeng <sui.jingfeng@linux.dev>
To: yetist <yetist@gmail.com>, Huacai Chen <chenhuacai@loongson.cn>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Huacai Chen <chenhuacai@kernel.org>
Cc: "loongson-kernel@lists.loongnix.cn"
<loongson-kernel@lists.loongnix.cn>,
dri-devel@lists.freedesktop.org
Subject: Re: drm/loongson: Error out if no VRAM detected
Date: Sun, 21 Jan 2024 05:09:24 +0800 [thread overview]
Message-ID: <5c5963ff-a534-48cc-8f9f-f4fdf148a78b@linux.dev> (raw)
In-Reply-To: <4144ea1c-f500-43b6-8641-ea21acae3376@gmail.com>
Hi,
On 2024/1/21 00:07, yetist wrote:
> Without this patch, my server cannot start the DM. It is a Loongson
> 3C5000L server, with both a Loongson display controller and an ASPEED
> graphics card.
>
> $ lspci |grep VGA
> 0000:00:06.1 VGA Compatible Controller: Loongson Technology LLC DC
> (Display Controller) (rev 01)
> 0000:03:00.0 VGA-compatible controller: ASPEED Technology, Inc.
> ASPEED Graphics Family (revision 41)
>
> When not working, there is the following information in dmesg:
>
> loongson 0000:00:06.1: [drm] Private vram start: 0xe00472a6000,
> size: 0MiB
> Loongson 0000:00:06.1: [drm] *Error* Request (0MiB) failed
>
>
> Anyway, this patch works fine with my server now, thank you.
>
Does the sever you are using has a dedicated VRAM for the 0000:00:06.1?
If not, the driver shouldn't be probed. This also means that the 0000:00:06.1
(Display Controller) shouldn't be detected by Linux kernel, because there is
no way for this driver can works correctly on such a case.
next prev parent reply other threads:[~2024-01-20 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:40 [PATCH] drm/loongson: Error out if no VRAM detected Huacai Chen
2024-01-19 16:18 ` Sui JIngfeng
2024-01-20 10:15 ` Katyusha
2024-01-20 12:01 ` Katyusha
2024-01-20 21:28 ` Sui JIngfeng
2024-01-21 7:07 ` Katyusha
2024-01-23 13:10 ` Sui Jingfeng
2024-01-20 16:07 ` yetist
2024-01-20 21:09 ` Sui JIngfeng [this message]
2024-01-21 8:45 ` yetist
2024-01-24 10:06 ` Huacai Chen
2024-01-23 1:21 ` [PATCH] " Shi Pujin
2024-02-02 17:24 ` Sui Jingfeng
2024-02-06 4:05 ` Huacai Chen
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=5c5963ff-a534-48cc-8f9f-f4fdf148a78b@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=airlied@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=yetist@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.