From: Thomas Zimmermann <tzimmermann@suse.de>
To: Pierre Asselin <pa@panix.com>, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v3] firmware/sysfb: Fix VESA format selection
Date: Fri, 21 Apr 2023 14:37:21 +0200 [thread overview]
Message-ID: <2f4370b6-8426-400a-8be1-36a48dadccad@suse.de> (raw)
In-Reply-To: <20230420155705.21463-1-pa@panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 3189 bytes --]
Hi
Am 20.04.23 um 17:57 schrieb Pierre Asselin:
> Some legacy BIOSes report no reserved bits in their 32-bit rgb mode,
> breaking the calculation of bits_per_pixel in commit f35cd3fa7729
> ("firmware/sysfb: Fix EFI/VESA format selection"). However they report
> lfb_depth correctly for those modes. Keep the computation but
> set bits_per_pixel to lfb_depth if the latter is larger.
>
> v2 fixes the warnings from a max3() macro with arguments of different
> types; split the bits_per_pixel assignment to avoid uglyfing the code
> with too many casts.
>
> v3 fixes space and formatting blips pointed out by Javier, and change
> the bit_per_pixel assignment back to a single statement using two casts.
>
> Link: https://lore.kernel.org/r/4Psm6B6Lqkz1QXM@panix3.panix.com
> Link: https://lore.kernel.org/r/20230412150225.3757223-1-javierm@redhat.com
> Link: https://lore.kernel.org/dri-devel/20230418183325.2327-1-pa@panix.com/T/#u
> Link: https://lore.kernel.org/dri-devel/20230419044834.10816-1-pa@panix.com/T/#u
> Fixes: f35cd3fa7729 ("firmware/sysfb: Fix EFI/VESA format selection")
> Signed-off-by: Pierre Asselin <pa@panix.com>
> ---
> drivers/firmware/sysfb_simplefb.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/firmware/sysfb_simplefb.c b/drivers/firmware/sysfb_simplefb.c
> index 82c64cb9f531..6f7c5d0c5090 100644
> --- a/drivers/firmware/sysfb_simplefb.c
> +++ b/drivers/firmware/sysfb_simplefb.c
> @@ -51,15 +51,18 @@ __init bool sysfb_parse_mode(const struct screen_info *si,
> *
> * It's not easily possible to fix this in struct screen_info,
> * as this could break UAPI. The best solution is to compute
> - * bits_per_pixel here and ignore lfb_depth. In the loop below,
> + * bits_per_pixel from the color bits, reserved bits and
> + * reported lfb_depth, whichever is highest. In the loop below,
> * ignore simplefb formats with alpha bits, as EFI and VESA
> * don't specify alpha channels.
> */
> if (si->lfb_depth > 8) {
> - bits_per_pixel = max(max3(si->red_size + si->red_pos,
> - si->green_size + si->green_pos,
> - si->blue_size + si->blue_pos),
> - si->rsvd_size + si->rsvd_pos);
> + /* max() macros args should be of the same type */
> + bits_per_pixel = max3((u16)max3(si->red_size + si->red_pos,
> + si->green_size + si->green_pos,
> + si->blue_size + si->blue_pos),
> + (u16)(si->rsvd_size + si->rsvd_pos),
> + si->lfb_depth);
I found this casting mess even more unreadable. I went back to v2, fixed
the style issues and committed the patch as v4 (still under your name).
https://cgit.freedesktop.org/drm/drm-tip/commit/?id=1b617bc93178912fa36f87a957c15d1f1708c299
Thanks a lot for the bugfix.
Best regard
Thomas
> } else {
> bits_per_pixel = si->lfb_depth;
> }
>
> base-commit: 6a8f57ae2eb07ab39a6f0ccad60c760743051026
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-04-21 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:57 Pierre Asselin
2023-04-20 16:05 ` Pierre Asselin
2023-04-21 11:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-21 11:35 ` Thomas Zimmermann
2023-04-21 13:42 ` Pierre Asselin
2023-04-21 12:37 ` Thomas Zimmermann [this message]
2023-05-10 17:25 ` Pierre Asselin
2023-05-11 8:05 ` Thomas Zimmermann
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=2f4370b6-8426-400a-8be1-36a48dadccad@suse.de \
--to=tzimmermann@suse.de \
--cc=ardb@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pa@panix.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
all inboxes | Powered by JetHome®