From: "Michel Dänzer" <michel@daenzer.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Set depth on low mem to 16 bpp instead of 8 bpp
Date: Tue, 18 Jul 2017 16:53:48 -0400 [thread overview]
Message-ID: <7ad0c34d-0efe-c54e-28fb-fc5ba31f1700@daenzer.net> (raw)
In-Reply-To: <20170718152053.15050-1-tiwai@suse.de>
On 18/07/17 11:20 AM, Takashi Iwai wrote:
> From: Egbert Eich <eich@suse.de>
>
> The radeon driver reduces the framebuffer resolution to 8bpp if a
> device with less than 32MB VRAM is found. This causes the framebuffer
> to run in 8 bit paletted mode. For a text console this is not an
> issue as 256 different colors is more than one gets on a VGA text
> console. However this leads to a poor 8bit pseudo-color visual when
> running X on fbdev, too, which is quite ugly.
>
> In this patch, we try to give some moderate compromise: limit the
> framebuffer bpp to 8 only when VRAM is 8MB or less, and use 16 bpp
> otherwise for 32MB or less VRAM.
>
> Signed-off-by: Egbert Eich <eich@suse.de>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
>
> This has been included in SUSE kernel for quite some time, and I'm
> trying to upstream this. The 16bpp looks more reasonable nowadays,
> but I know this is a matter of taste, too. It'd be great if you guys
> can comment on this, at least, whether it's uttly non-sense or not.
[...]
> diff --git a/drivers/gpu/drm/radeon/radeon_fb.c b/drivers/gpu/drm/radeon/radeon_fb.c
> index 356ad90a5238..b5f2642f124b 100644
> --- a/drivers/gpu/drm/radeon/radeon_fb.c
> +++ b/drivers/gpu/drm/radeon/radeon_fb.c
> @@ -347,9 +347,12 @@ int radeon_fbdev_init(struct radeon_device *rdev)
> if (list_empty(&rdev->ddev->mode_config.connector_list))
> return 0;
>
> - /* select 8 bpp console on RN50 or 16MB cards */
> - if (ASIC_IS_RN50(rdev) || rdev->mc.real_vram_size <= (32*1024*1024))
> + /* select 8 bpp console on 8MB cards, or 16 bpp on RN50 or 32MB */
> + if (rdev->mc.real_vram_size <= (8*1024*1024))
> bpp_sel = 8;
> + else if (ASIC_IS_RN50(rdev) ||
> + rdev->mc.real_vram_size <= (32*1024*1024))
> + bpp_sel = 16;
>
> rfbdev = kzalloc(sizeof(struct radeon_fbdev), GFP_KERNEL);
> if (!rfbdev)
>
Looks reasonable to me — if nothing else, at least the comment and code
will match again! :)
My only potential doubt is whether there could be another reason than
VRAM size why RN50 should use 8 bpp. Assuming not,
Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-18 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 15:20 [PATCH] drm/radeon: Set depth on low mem to 16 bpp instead of 8 bpp Takashi Iwai
2017-07-18 20:53 ` Michel Dänzer [this message]
[not found] ` <7ad0c34d-0efe-c54e-28fb-fc5ba31f1700-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-07-19 8:45 ` Takashi Iwai
[not found] ` <s5hk23495mu.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
2017-07-24 20:46 ` Alex Deucher
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=7ad0c34d-0efe-c54e-28fb-fc5ba31f1700@daenzer.net \
--to=michel@daenzer.net \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tiwai@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).