dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: mgag200 broken on kernel-6.0-rc3 on DELL/T620
Date: Wed, 14 Sep 2022 09:59:39 +0200	[thread overview]
Message-ID: <86e3a684-7a50-ed05-a89d-eeef154b2e67@suse.de> (raw)
In-Reply-To: <20220913231522.7CAA.409509F4@e16-tech.com>


[-- Attachment #1.1: Type: text/plain, Size: 1915 bytes --]

Hi

Am 13.09.22 um 17:15 schrieb Wang Yugui:
[...]
>>>
>>> so I tried to revert patch of mgag200 driver in batch of 2 or 3, the I
>>> noticed the patch 'Subject: drm/mgag200: Remove special case for G200SE
>>> with <2 MiB' and then tried this dirty fix.
>>
>> Oh, great work! Thank you. From looking at the screenshot that you provided, it seems as if the 24-bit mode setting is broken. I'm not sure why the G200SE workaround applies to a G200ER, but we'll see.
> 
> I tested 'preferred_depth = 32' too. it works on T630 too.
> 
> so both 16 and 32 work, but 24 failed on DELL/T630.

I tried on my test machine with a 5.19 kernel and found that 32-bit and 
24-bit pixels work, but 16-bit looks incorrect.

What are the results if you boot your kernel 5.19.3 with the parameter 
video=1024x768-24? This should enable 24-bit pixels.

How does video=1024x768-16 look with the 5.19 kernel?

Best regards
Thomas

> 
> diff --git a/drivers/gpu/drm/mgag200/mgag200_mode.c
> b/drivers/gpu/drm/mgag200/mgag200_mode.c
> index 225cca2ed60e..563e3ab05fbc 100644
> --- a/drivers/gpu/drm/mgag200/mgag200_mode.c
> +++ b/drivers/gpu/drm/mgag200/mgag200_mode.c
> @@ -1070,7 +1070,7 @@ int mgag200_modeset_init(struct mga_device *mdev, resource_size_t vram_available
> 
>          dev->mode_config.max_width = MGAG200_MAX_FB_WIDTH;
>          dev->mode_config.max_height = MGAG200_MAX_FB_HEIGHT;
> -       dev->mode_config.preferred_depth = 24;
> +       dev->mode_config.preferred_depth = 32;
>          dev->mode_config.fb_base = mdev->vram_res->start;
>          dev->mode_config.funcs = &mgag200_mode_config_funcs;
> 
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2022/09/13
> 
> 
> 

-- 
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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-09-14  7:59 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 [this message]
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

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=86e3a684-7a50-ed05-a89d-eeef154b2e67@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=wangyugui@e16-tech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox