All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Atharva Tiwari <evepolonium@gmail.com>
Cc: evepolonium@gmail.com, Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/i915/fbdev: Discard large BIOS framebuffers
Date: Tue, 21 Jan 2025 14:05:49 +0200	[thread overview]
Message-ID: <87ldv4pe1u.fsf@intel.com> (raw)
In-Reply-To: <20250121104210.3159-1-evepolonium@gmail.com>

On Tue, 21 Jan 2025, Atharva Tiwari <evepolonium@gmail.com> wrote:
> On certain 4K panels, the BIOS framebuffer
> exceeds the panel's required dimensions,
> leading to display corruption.
> This patch introduces a validation check to address the issue.
>
> Signed-off-by: Atharva Tiwari <evepolonium@gmail.com>

See [1], [2], and [3].

Please add your dmesg with debugs enabled to [3].

BR,
Jani.


[1] https://lore.kernel.org/r/31D69334-DEF9-41B7-968B-B847796926FF@outlook.com

[2] https://lore.kernel.org/r/Yd7ZnBlU0sjP4qcG@intel.com

[3] https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13466


> ---
>  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 00852ff5b247..e8cf06772c31 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
> @@ -197,10 +197,10 @@ static int intelfb_create(struct drm_fb_helper *helper,
>  	ifbdev->fb = NULL;
>  
>  	if (fb &&
> -	    (sizes->fb_width > fb->base.width ||
> -	     sizes->fb_height > fb->base.height)) {
> +	    (sizes->fb_width != fb->base.width ||
> +	     sizes->fb_height != fb->base.height)) {
>  		drm_dbg_kms(&dev_priv->drm,
> -			    "BIOS fb too small (%dx%d), we require (%dx%d),"
> +			    "BIOS fb dimensions mismatch (%dx%d), we require (%dx%d),"
>  			    " releasing it\n",
>  			    fb->base.width, fb->base.height,
>  			    sizes->fb_width, sizes->fb_height);

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-01-21 12:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 10:42 [PATCH] drm/i915/fbdev: Discard large BIOS framebuffers Atharva Tiwari
2025-01-21 12:05 ` Jani Nikula [this message]
2025-01-21 16:59 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-21 17:00 ` ✓ CI.checkpatch: " Patchwork
2025-01-21 17:02 ` ✓ CI.KUnit: " Patchwork
2025-01-21 17:19 ` ✓ CI.Build: " Patchwork
2025-01-21 17:21 ` ✓ CI.Hooks: " Patchwork
2025-01-21 17:22 ` ✓ CI.checksparse: " Patchwork
2025-01-21 17:49 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-21 18:55 ` ✓ i915.CI.BAT: " Patchwork
2025-01-21 23:10 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-22 10:33 ` ✗ i915.CI.Full: " Patchwork

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=87ldv4pe1u.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=evepolonium@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=ville.syrjala@linux.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.