From: "Pierre Asselin" <pa@panix.com>
To: "Javier Martinez Canillas" <javierm@redhat.com>
Cc: "Pierre Asselin" <pa@panix.com>,
"Jocelyn Falempe" <jfalempe@redhat.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Hans de Goede" <hdegoede@redhat.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [PATCH] firmware/sysfb: Fix wrong stride when bits-per-pixel is calculated
Date: Wed, 12 Apr 2023 19:13:35 -0400 [thread overview]
Message-ID: <9e6fff69b09b36cbdd96499cd0015154.squirrel@mail.panix.com> (raw)
In-Reply-To: <87a5zcsqg8.fsf@minerva.mail-host-address-is-not-set>
(Okay, can't back out *all* of the first patch, just the assignment
to mode->stride.)
Anyway, here you go:
grub: gfxpayload=keep
[ 0.003333] Console: colour dummy device 128x48
[ 0.003333] printk: console [tty0] enabled
[ 0.419983] fbcon: Taking over console
[ 0.516198] pci 0000:01:05.0: vgaarb: setting as boot VGA device
[ 0.516229] pci 0000:01:05.0: vgaarb: bridge control possible
[ 0.516253] pci 0000:01:05.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[ 0.516288] vgaarb: loaded
[ 3.343649] simple-framebuffer simple-framebuffer.0: framebuffer at
0xd8000000, 0x300000 bytes
[ 3.343687] simple-framebuffer simple-framebuffer.0: format=r8g8b8,
mode=1024x768x24, linelength=4096
[ 3.344199] Console: switching to colour frame buffer device 128x48
[ 3.681177] simple-framebuffer simple-framebuffer.0: fb0: simplefb
registered!
[ 3.343345] sysfb: si->lfb_depth 32 si->lfb_width 1024
[ 3.343372] sysfb: si->red_size 8 si->red_pos 16
[ 3.343392] sysfb: si->green_size 8 si->green_pos 8
[ 3.343413] sysfb: si->blue_size 8 si->blue_pos 0
[ 3.343433] sysfb: si->rsvd_size 0 si->rsvd_pos 0
[ 3.343453] sysfb: bits_per_pixel 24 si->lfb_linelength 4096
[ 3.343476] sysfb: stride 3072
[ 3.343493] sysfb: format r8g8b8
So it's the rsvd_size and rsvd_pos that are bogus. The fix would be to:
1) believe si->lfb_depth
2) fill with ones a bitmask of size si->lfb_depth
3) clear chunks of bits based on si->{red,green,blue,rsvd}_{size,pos}
4) printk if the bitmask is not all zeros
5) override rsvd_{size,pos} based on the bitmask
That way you know where the 'x' goes in xrgb.
Hm. Could that fix my two boxes but cause a regression for someone else ?
What if _depth is low but the rsvd_ are right ?
Then _width and _linelength would be inconsistent with _depth but
consistent with the recomputed bits_per_pixel ? How many ways can the
firmware lie ?
We need more testers, don't we ?
next prev parent reply other threads:[~2023-04-12 23:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 15:02 [PATCH] firmware/sysfb: Fix wrong stride when bits-per-pixel is calculated Javier Martinez Canillas
2023-04-12 16:18 ` Pierre Asselin
2023-04-12 17:31 ` Javier Martinez Canillas
2023-04-12 18:12 ` Pierre Asselin
2023-04-12 18:24 ` Javier Martinez Canillas
2023-04-12 18:51 ` Pierre Asselin
2023-04-12 21:04 ` Javier Martinez Canillas
2023-04-12 21:40 ` Javier Martinez Canillas
2023-04-12 21:53 ` Pierre Asselin
2023-04-12 22:09 ` Javier Martinez Canillas
2023-04-12 23:13 ` Pierre Asselin [this message]
2023-04-13 1:13 ` Pierre Asselin
2023-04-13 1:34 ` Pierre Asselin
2023-04-17 8:15 ` Thomas Zimmermann
2023-04-17 8:58 ` Javier Martinez Canillas
2023-04-17 9:15 ` Thomas Zimmermann
2023-04-17 9:29 ` Javier Martinez Canillas
2023-04-13 7:08 ` Javier Martinez Canillas
2023-04-13 16:24 ` Pierre Asselin
2023-04-13 16:34 ` Javier Martinez Canillas
2023-04-13 17:17 ` Pierre Asselin
2023-04-13 18:04 ` Javier Martinez Canillas
2023-04-13 6:54 ` Javier Martinez Canillas
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=9e6fff69b09b36cbdd96499cd0015154.squirrel@mail.panix.com \
--to=pa@panix.com \
--cc=ardb@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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