From: Wang Yugui <wangyugui@e16-tech.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Jocelyn Falempe <jfalempe@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: mgag200 broken on kernel-6.0-rc3 on DELL/T620
Date: Tue, 20 Sep 2022 17:02:20 +0800 [thread overview]
Message-ID: <20220920170219.788D.409509F4@e16-tech.com> (raw)
In-Reply-To: <16995c0f-c698-b1b0-0311-73882aef5f75@suse.de>
Hi,
> Hi
>
> Am 15.09.22 um 16:41 schrieb Wang Yugui:
> > Hi,
> >
> >> Hi
> >>
> >> Am 14.09.22 um 16:58 schrieb Wang Yugui:
> >> [...]
> >>>> 24-bit works on my G200HE and G200 test machines. Maybe the G200ER has a bug.
> >>>>
> >>>> When I try 16-bit depth, the display works, but is way too dark. No fiddling with the LUT tables fixes this. It's 90s hardware, so it should support 16-bit framebuffers well, but there's no obvious bug to be seen.
> >>>>
> >>>> I guess, we could remove 16 and 24 bit support for now if nothing else helps.
> >>>
> >>>
> >>> maybe better if we revert 73f54d5d9682 (drm/mgag200: Remove special case
> >>> for G200SE with <2 MiB)
> >>
> >> Could you please test the attached patch on the 6.0-rc3 kernel? It should force the driver to a correct color format if no kernel parameters are given.
> >>
> >
> > This patch works well.
>
> I have meanwhile added the patch to drm-misc-fixes. We want to add a workaround for your machine to the driver. Can you please send me the output of
>
> sudo dmidecode -s system-manufacturer
>
> and
>
> sudo dmidecode -s system-product-name
>
DELL/T630
[root@T630 ~]# dmidecode -s system-manufacturer
Dell Inc.
[root@T630 ~]# dmidecode -s system-product-name
PowerEdge T630
DELL/T620
[root@T620 ~]# dmidecode -s system-manufacturer
Dell Inc.
[root@T620 ~]# dmidecode -s system-product-name
PowerEdge T620
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2022/09/20
> Best regards
> Thomas
>
> >
> > test case detail:
> > kernel parm video is not given
> > server DELL/T620
> > kernel is 6.0-rc5
> >
> > Best Regards
> > Wang Yugui (wangyugui@e16-tech.com)
> > 2022/09/15
> >
> >
> >> Best regards
> >> Thomas
> >>
> >>>
> >>> because there is no test result on device G200_SE
> >>>
> >>> static unsigned int mgag200_preferred_depth(struct mga_device *mdev)
> >>> {
> >>> if (IS_G200_SE(mdev) && mdev->vram_fb_available < (2048*1024))
> >>> return 16;
> >>> else
> >>> return 32;
> >>> }
> >>>
> >>> Best Regards
> >>> Wang Yugui (wangyugui@e16-tech.com)
> >>> 2022/09/14
> >>>
> >> -- Thomas Zimmermann
> >> Graphics Driver Developer
> >> SUSE Software Solutions Germany GmbH
> >> Maxfeldstr. 5, 90409 Nürnberg, Germany
> >> (HRB 36809, AG Nürnberg)
> >> Gesch?ftsführer: Ivo Totev
> >
> >
> -- Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Gesch?ftsführer: Ivo Totev
prev parent reply other threads:[~2022-09-20 9:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220902135242.2447.409509F4@e16-tech.com>
2022-09-05 6:57 ` mgag200 broken on kernel-6.0-rc3 on DELL/T620 Thomas Zimmermann
2022-09-07 4:16 ` Wang Yugui
2022-09-07 6:47 ` Thomas Zimmermann
2022-09-07 7:38 ` Wang Yugui
2022-09-07 7:55 ` Thomas Zimmermann
2022-09-07 8:47 ` Wang Yugui
2022-09-07 9:18 ` Thomas Zimmermann
2022-09-13 8:34 ` Thomas Zimmermann
2022-09-13 14:25 ` Wang Yugui
2022-09-13 14:44 ` Thomas Zimmermann
2022-09-13 15:15 ` Wang Yugui
2022-09-14 7:59 ` Thomas Zimmermann
2022-09-14 8:29 ` Wang Yugui
2022-09-14 14:36 ` Thomas Zimmermann
2022-09-14 14:58 ` Wang Yugui
2022-09-14 15:41 ` Thomas Zimmermann
2022-09-14 16:25 ` Wang Yugui
2022-09-15 12:54 ` Thomas Zimmermann
2022-09-15 14:41 ` Wang Yugui
2022-09-20 7:57 ` Thomas Zimmermann
2022-09-20 9:02 ` Wang Yugui [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=20220920170219.788D.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).