All of lore.kernel.org
 help / color / mirror / Atom feed
From: Orlando Chamberlain <redecorating@protonmail.com>
To: jani.nikula@linux.intel.com
Cc: ashisharora.linux@outlook.com, intel-gfx@lists.freedesktop.org,
	joonas.lahtinen@linux.intel.com, linux-kernel@vger.kernel.org,
	rodrigo.vivi@intel.com, Aun-Ali Zaidi <admin@kodeit.net>
Subject: Re: [PATCH] drm/i915: Discard large BIOS framebuffers causing display corruption.
Date: Sat, 08 Jan 2022 05:11:50 +0000	[thread overview]
Message-ID: <20220108050812.6303-1-redecorating@protonmail.com> (raw)

I haven't observed "display corruption", but on my MacBookPro16,1 the bottom
and right edges of the TTY are not on the screen, so a few lines of text
cannot be seen.

This also occurs on the internal displays of all (as far as I know) other
2018-2020 Intel Macbooks when using the Intel GPU (The 15" and 16" ones
also have an AMDGPU, but this issue occurs when they have the Intel GPU
set as the boot gpu).

There's a similar patch that hasn't been sent upstream that people with these
Macbooks have been using:
https://github.com/aunali1/linux-mbp-arch/blob/master/7001-drm-i915-fbdev-Discard-BIOS-framebuffers-exceeding-h.patch

Cc: Aun-Ali Zaidi <admin@kodeit.net>

--
Thanks,
Orlando


WARNING: multiple messages have this Message-ID (diff)
From: Orlando Chamberlain <redecorating@protonmail.com>
To: jani.nikula@linux.intel.com
Cc: Aun-Ali Zaidi <admin@kodeit.net>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	ashisharora.linux@outlook.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Discard large BIOS framebuffers causing display corruption.
Date: Sat, 08 Jan 2022 05:11:50 +0000	[thread overview]
Message-ID: <20220108050812.6303-1-redecorating@protonmail.com> (raw)

I haven't observed "display corruption", but on my MacBookPro16,1 the bottom
and right edges of the TTY are not on the screen, so a few lines of text
cannot be seen.

This also occurs on the internal displays of all (as far as I know) other
2018-2020 Intel Macbooks when using the Intel GPU (The 15" and 16" ones
also have an AMDGPU, but this issue occurs when they have the Intel GPU
set as the boot gpu).

There's a similar patch that hasn't been sent upstream that people with these
Macbooks have been using:
https://github.com/aunali1/linux-mbp-arch/blob/master/7001-drm-i915-fbdev-Discard-BIOS-framebuffers-exceeding-h.patch

Cc: Aun-Ali Zaidi <admin@kodeit.net>

--
Thanks,
Orlando


             reply	other threads:[~2022-01-08  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  5:11 Orlando Chamberlain [this message]
2022-01-08  5:11 ` [Intel-gfx] [PATCH] drm/i915: Discard large BIOS framebuffers causing display corruption Orlando Chamberlain
2022-01-08  8:55 ` Ashish Arora
2022-01-08  9:59 ` Ashish Arora
2022-01-08 10:26   ` Aun-Ali Zaidi
2022-01-08 10:26     ` [Intel-gfx] " Aun-Ali Zaidi
2022-01-08 10:43     ` Ashish Arora
  -- strict thread matches above, loose matches on Subject: below --
2022-01-07 12:35 Ashish Arora
2022-01-07 12:47 ` Jani Nikula
2022-01-07 13:59   ` 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=20220108050812.6303-1-redecorating@protonmail.com \
    --to=redecorating@protonmail.com \
    --cc=admin@kodeit.net \
    --cc=ashisharora.linux@outlook.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --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.