From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ashish Arora <ashisharora.linux@outlook.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH - v3] drm/i915: Discard large BIOS framebuffers causing display corruption.
Date: Tue, 11 Jan 2022 10:36:46 +0200 [thread overview]
Message-ID: <87v8yq8y8x.fsf@intel.com> (raw)
In-Reply-To: <31D69334-DEF9-41B7-968B-B847796926FF@outlook.com>
On Tue, 11 Jan 2022, Ashish Arora <ashisharora.linux@outlook.com> wrote:
> From: Ashish Arora <ashisharora.linux@outlook.com>
>
> On certain 4k panels and Macs, the BIOS framebuffer is larger than what
> panel requires causing display corruption. Introduce a check for the same.
>
>
> Signed-off-by: Ashish Arora <ashisharora.linux@outlook.com>
> Reviewed-by: Aun-Ali Zaidi <admin@kodeit.net>
I'll defer to Ville on this one, Cc'd.
BR,
Jani.
> ---
> V2 :- Use != instead of < and >
> V3 :- Mention Macs (Thanks to Orlando)
> drivers/gpu/drm/i915/display/intel_fbdev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c b/drivers/gpu/drm/i915/display/intel_fbdev.c
> index 842c04e63..16b1c82b2 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
> @@ -181,10 +181,10 @@ static int intelfb_create(struct drm_fb_helper *helper,
> int ret;
>
> if (intel_fb &&
> - (sizes->fb_width > intel_fb->base.width ||
> - sizes->fb_height > intel_fb->base.height)) {
> + (sizes->fb_width != intel_fb->base.width ||
> + sizes->fb_height != intel_fb->base.height)) {
> drm_dbg_kms(&dev_priv->drm,
> - "BIOS fb too small (%dx%d), we require (%dx%d),"
> + "BIOS fb not valid (%dx%d), we require (%dx%d),"
> " releasing it\n",
> intel_fb->base.width, intel_fb->base.height,
> sizes->fb_width, sizes->fb_height);
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ashish Arora <ashisharora.linux@outlook.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
ville.syrjala@linux.intel.com
Subject: Re: [PATCH - v3] drm/i915: Discard large BIOS framebuffers causing display corruption.
Date: Tue, 11 Jan 2022 10:36:46 +0200 [thread overview]
Message-ID: <87v8yq8y8x.fsf@intel.com> (raw)
In-Reply-To: <31D69334-DEF9-41B7-968B-B847796926FF@outlook.com>
On Tue, 11 Jan 2022, Ashish Arora <ashisharora.linux@outlook.com> wrote:
> From: Ashish Arora <ashisharora.linux@outlook.com>
>
> On certain 4k panels and Macs, the BIOS framebuffer is larger than what
> panel requires causing display corruption. Introduce a check for the same.
>
>
> Signed-off-by: Ashish Arora <ashisharora.linux@outlook.com>
> Reviewed-by: Aun-Ali Zaidi <admin@kodeit.net>
I'll defer to Ville on this one, Cc'd.
BR,
Jani.
> ---
> V2 :- Use != instead of < and >
> V3 :- Mention Macs (Thanks to Orlando)
> drivers/gpu/drm/i915/display/intel_fbdev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c b/drivers/gpu/drm/i915/display/intel_fbdev.c
> index 842c04e63..16b1c82b2 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
> @@ -181,10 +181,10 @@ static int intelfb_create(struct drm_fb_helper *helper,
> int ret;
>
> if (intel_fb &&
> - (sizes->fb_width > intel_fb->base.width ||
> - sizes->fb_height > intel_fb->base.height)) {
> + (sizes->fb_width != intel_fb->base.width ||
> + sizes->fb_height != intel_fb->base.height)) {
> drm_dbg_kms(&dev_priv->drm,
> - "BIOS fb too small (%dx%d), we require (%dx%d),"
> + "BIOS fb not valid (%dx%d), we require (%dx%d),"
> " releasing it\n",
> intel_fb->base.width, intel_fb->base.height,
> sizes->fb_width, sizes->fb_height);
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-11 8:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 7:55 [Intel-gfx] [PATCH - v3] drm/i915: Discard large BIOS framebuffers causing display corruption Ashish Arora
2022-01-11 8:36 ` Jani Nikula [this message]
2022-01-11 8:36 ` Jani Nikula
2022-01-11 18:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Discard large BIOS framebuffers causing display corruption. (rev3) Patchwork
2022-01-11 23:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-01-12 13:37 ` [Intel-gfx] [PATCH - v3] drm/i915: Discard large BIOS framebuffers causing display corruption Ville Syrjälä
2022-01-12 13:37 ` Ville Syrjälä
2022-01-12 13:42 ` Ashish Arora
2022-01-30 9:27 ` Ashish Arora
2025-01-03 11:15 ` [BUG] The bottom and right edges on the tty are not shown on Apple T2 MacBooks with Retina display Aditya Garg
2025-01-03 14:14 ` Jani Nikula
2025-01-07 12:25 ` Aditya Garg
2025-01-07 12:32 ` Jani Nikula
2025-01-07 14:32 ` Aditya Garg
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=87v8yq8y8x.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ashisharora.linux@outlook.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.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 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.