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 14:51:10 -0400 [thread overview]
Message-ID: <1afd3044c2aca9322ecf304941c7df66.squirrel@mail.panix.com> (raw)
In-Reply-To: <CAFOAJEdKBUg91pDmNYYw5xigUxjifBgOLz2YgD+xQ+WyEy=V2w@mail.gmail.com>
> And can you share the "linelength=" print out from simplefb ?
Okay. Three cases, see below.
Your patch tries to fix the stride, but what if it's the _depth_
that's wrong ? Grub sets the mode, the pre-regression kernel picks this:
format=x8r8g8b8, mode=1024x768x32, linelength=4096
========== Good ======================================================
grub: gfxpayload=1024x768x24
[ 0.003333] Console: colour dummy device 128x48
[ 0.003333] printk: console [tty0] enabled
[ 0.417054] fbcon: Taking over console
[ 0.513399] pci 0000:01:05.0: vgaarb: setting as boot VGA device
[ 0.513431] pci 0000:01:05.0: vgaarb: bridge control possible
[ 0.513455] pci 0000:01:05.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[ 0.513490] vgaarb: loaded
[ 3.337529] simple-framebuffer simple-framebuffer.0: framebuffer at
0xd8000000, 0x240000 bytes
[ 3.337567] simple-framebuffer simple-framebuffer.0: format=r8g8b8,
mode=1024x768x24, linelength=3072
[ 3.338000] Console: switching to colour frame buffer device 128x48
[ 3.566490] simple-framebuffer simple-framebuffer.0: fb0: simplefb
registered!
========== Bad after patch, typing blind to log in !==================
grub: gfxpayload=keep
[ 0.003333] Console: colour dummy device 128x48
[ 0.003333] printk: console [tty0] enabled
[ 0.423925] fbcon: Taking over console
[ 0.520030] pci 0000:01:05.0: vgaarb: setting as boot VGA device
[ 0.520061] pci 0000:01:05.0: vgaarb: bridge control possible
[ 0.520085] pci 0000:01:05.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[ 0.520120] vgaarb: loaded
[ 3.290444] simple-framebuffer simple-framebuffer.0: framebuffer at
0xd8000000, 0x240000 bytes
[ 3.290483] simple-framebuffer simple-framebuffer.0: format=r8g8b8,
mode=1024x768x24, linelength=3072
[ 3.290916] Console: switching to colour frame buffer device 128x48
[ 3.519523] simple-framebuffer simple-framebuffer.0: fb0: simplefb
registered!
========== Good, earlier kernel before regression ====================
grub: gfxpayload=keep
[ 0.226675] Console: colour dummy device 128x48
[ 0.228643] printk: console [tty0] enabled
[ 0.429214] fbcon: Taking over console
[ 0.524994] pci 0000:01:05.0: vgaarb: setting as boot VGA device
[ 0.525025] pci 0000:01:05.0: vgaarb: bridge control possible
[ 0.525049] pci 0000:01:05.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[ 0.525082] vgaarb: loaded
[ 3.320474] simple-framebuffer simple-framebuffer.0: framebuffer at
0xd8000000, 0x300000 bytes
[ 3.320513] simple-framebuffer simple-framebuffer.0: format=x8r8g8b8,
mode=1024x768x32, linelength=4096
[ 3.320983] Console: switching to colour frame buffer device 128x48
[ 3.415643] simple-framebuffer simple-framebuffer.0: fb0: simplefb
registered!
next prev parent reply other threads:[~2023-04-12 18:51 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 [this message]
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
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=1afd3044c2aca9322ecf304941c7df66.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