From: Lukas Wunner <lukas@wunner.de>
To: Aditya Garg <gargaditya08@live.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Kerem Karabay <kekrby@gmail.com>,
Orlando Chamberlain <orlandoch.dev@gmail.com>,
"sharpenedblade@proton.me" <sharpenedblade@proton.me>
Subject: Re: [PATCH v3 0/2] efi/x86: Call set_os() protocol on dual GPU Macs
Date: Wed, 24 Jul 2024 18:28:17 +0200 [thread overview]
Message-ID: <ZqEroUgkB-J-JG4D@wunner.de> (raw)
In-Reply-To: <MA0P287MB0217AA8547F79B36B754A7B2B8AA2@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM>
On Wed, Jul 24, 2024 at 04:21:03PM +0000, Aditya Garg wrote:
> https://www.phoronix.com/forums/forum/software/general-linux-open-source/1479158-linux-6-11-efi-will-fake-that-it-s-booting-apple-macos-to-fix-some-dual-gpu-macs?p=1479205#post1479205
>
> By looking at this post, it seems to affect non T2 Macs as well.
Disabling iGPU if dGPU is present was a behavior that existed well
before T2 Macs, yes. That affected MacBook Pros from Haswell onward.
However the question is since when iGPU is disabled if an eGPU is present.
I had never heard of this before. It would be good to have more datapoints
to come up with a quirk that's as narrowly applied as possible to avoid
regressions.
Thanks,
Lukas
next prev parent reply other threads:[~2024-07-24 16:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:09 [PATCH v3 0/2] efi/x86: Call set_os() protocol on dual GPU Macs Ard Biesheuvel
2024-07-01 14:09 ` [PATCH v3 1/2] efistub/x86: Enable SMBIOS protocol handling for x86 Ard Biesheuvel
2024-07-01 14:09 ` [PATCH v3 2/2] x86/efistub: Call Apple set_os protocol on dual GPU Intel Macs Ard Biesheuvel
2024-07-01 14:17 ` [PATCH v3 0/2] efi/x86: Call set_os() protocol on dual GPU Macs Lukas Wunner
2024-07-01 19:42 ` Aditya Garg
2024-07-17 16:35 ` Aditya Garg
2024-07-17 16:46 ` Ard Biesheuvel
2024-07-17 16:52 ` Aditya Garg
2024-07-17 18:27 ` Sharpened Blade
2024-07-17 18:58 ` Lukas Wunner
2024-07-23 16:25 ` Aditya Garg
2024-07-23 16:26 ` Aditya Garg
2024-07-24 16:01 ` Lukas Wunner
2024-07-24 16:21 ` Aditya Garg
2024-07-24 16:28 ` Lukas Wunner [this message]
2024-07-24 16:30 ` Aditya Garg
2024-07-24 16:26 ` Aditya Garg
2024-07-24 16:31 ` Lukas Wunner
2024-07-24 16:34 ` Aditya Garg
2024-07-25 12:42 ` Ard Biesheuvel
2024-07-25 12:58 ` Aditya Garg
2024-07-25 12:39 ` Ard Biesheuvel
2024-07-25 12:55 ` Aditya Garg
2024-07-28 12:03 ` Orlando Chamberlain
2024-07-29 7:27 ` Ard Biesheuvel
2024-07-29 7:46 ` 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=ZqEroUgkB-J-JG4D@wunner.de \
--to=lukas@wunner.de \
--cc=ardb@kernel.org \
--cc=gargaditya08@live.com \
--cc=hdegoede@redhat.com \
--cc=kekrby@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orlandoch.dev@gmail.com \
--cc=sharpenedblade@proton.me \
/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