linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Aditya Garg <gargaditya08@live.com>,
	Ashish Arora <ashisharora.linux@outlook.com>
Cc: "joonas.lahtinen@linux.intel.com"
	<joonas.lahtinen@linux.intel.com>,
	"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>,
	"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Orlando Chamberlain <orlandoch.dev@gmail.com>
Subject: Re: [BUG] The bottom and right edges on the tty are not shown on Apple T2 MacBooks with Retina display
Date: Fri, 03 Jan 2025 16:14:45 +0200	[thread overview]
Message-ID: <87bjwom1be.fsf@intel.com> (raw)
In-Reply-To: <02E00F62-D48C-4F34-9F81-BE75A1833795@live.com>

On Fri, 03 Jan 2025, Aditya Garg <gargaditya08@live.com> wrote:
> Hello maintainers
>
> This bug has been there for a long time, and hasn't been fixed yet. In case the Intel GPU is used as boot GPU on Apple T2 MacBooks, the bottom and right edges of the tty are no longer seen, thus making some text not visible.
>
> It has been reported in almost all Apple T2 MacBooks with Intel GPU, which have the Retina display.
>
> In case of a dual GPU MacBook, if the AMD dGPU is used to boot, the bug no longer exists.
>
> This patch below was submitted 3 years ago, and it fixes this issue.

Please file a bug as described at [1], attaching dmesg from boot with
debugs enabled, etc.

As suggested by Ville in [2], the bug is likely elsewhere, and this just
hides it. A bigger fb shouldn't be a problem, and we shouldn't add this
limitation everywhere because of the issue you're seeing.

BR,
Jani.



[1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html

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

>
>> On 11 Jan 2022, at 1:25 PM, 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>
>> ---
>> 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);
>> -- 
>> 2.25.1
>> 
>> 
>> 
>

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-01-03 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <31D69334-DEF9-41B7-968B-B847796926FF@outlook.com>
2022-01-11  8:36 ` [PATCH - v3] drm/i915: Discard large BIOS framebuffers causing display corruption Jani Nikula
2022-01-12 13:37 ` [Intel-gfx] " Ville Syrjälä
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 [this message]
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=87bjwom1be.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ashisharora.linux@outlook.com \
    --cc=gargaditya08@live.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orlandoch.dev@gmail.com \
    --cc=rodrigo.vivi@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).