From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
daniel@ffwll.ch, airlied@gmail.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, xinliang.liu@linaro.org,
tiantao6@hisilicon.com, jstultz@google.com,
kong.kongxinwei@hisilicon.com, puck.chen@hisilicon.com,
paul.kocialkowski@bootlin.com, airlied@redhat.com,
kraxel@redhat.com
Cc: dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 7/7] drm/fb-helper: Don't use the preferred depth for the BPP default
Date: Fri, 18 Nov 2022 15:12:59 +0100 [thread overview]
Message-ID: <8efa5cf1-4f32-53b9-49a4-bc3a44fbff14@redhat.com> (raw)
In-Reply-To: <20221116160917.26342-8-tzimmermann@suse.de>
On 11/16/22 17:09, Thomas Zimmermann wrote:
> If no preferred value for bits-per-pixel has been given, fall back
> to 32. Never use the preferred depth. The color depth is the number
> of color/alpha bits per pixel, while bpp is the overall number of
> bits in most cases.
>
> Most noteworthy, XRGB8888 has a depth of 24 and a bpp value of 32.
> Using depth for bpp would make the value 24 as well and format
> selection in fbdev helpers fails. Unfortunately XRGB8888 is the most
> common format and the old heuristic therefore fails for most of
> the drivers (unless they implement the 24-bit RGB888 format).
>
> Picking a bpp of 32 will lateron result in a default depth of 24
later on
> and the format XRGB8888. As XRGB8888 is the default format for most
> of the current and legacy graphics stack, all drivers must support
> it. So it is the safe choice.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
Agreed that 32 is a safe choice in this case.
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2022-11-18 14:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:09 [PATCH 0/7] drm: Fix the color-depth/bpp confusion Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-16 16:09 ` [PATCH 1/7] drm/hisilicon/hibmc: Fix preferred depth and bpp Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 12:52 ` Javier Martinez Canillas
2022-11-18 13:18 ` Thomas Zimmermann
2022-11-18 13:18 ` Thomas Zimmermann
2022-11-18 13:31 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 2/7] drm/logicvc: Fix preferred fbdev cpp Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 13:08 ` Javier Martinez Canillas
2022-11-18 13:22 ` Thomas Zimmermann
2022-11-18 13:22 ` Thomas Zimmermann
2022-11-18 13:41 ` Javier Martinez Canillas
2022-11-18 13:48 ` Thomas Zimmermann
2022-11-18 13:48 ` Thomas Zimmermann
2022-11-18 14:01 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 3/7] drm/cirrus: Decouple fbdev bpp value from color depth Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 13:44 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 4/7] drm/ofdrm: Set preferred depth from format of scanout buffer Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 14:06 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 5/7] drm/simpledrm: " Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 14:07 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 6/7] drm/solomon: Set preferred color depth and bpp to the correct values Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 14:08 ` Javier Martinez Canillas
2022-11-16 16:09 ` [PATCH 7/7] drm/fb-helper: Don't use the preferred depth for the BPP default Thomas Zimmermann
2022-11-16 16:09 ` Thomas Zimmermann
2022-11-18 14:12 ` Javier Martinez Canillas [this message]
2022-11-22 14:43 ` Daniel Vetter
2022-11-22 14:43 ` Daniel Vetter
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=8efa5cf1-4f32-53b9-49a4-bc3a44fbff14@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jstultz@google.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=kraxel@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=puck.chen@hisilicon.com \
--cc=tiantao6@hisilicon.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=xinliang.liu@linaro.org \
/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.