From: Lukas Wunner <lukas@wunner.de>
To: Aditya Garg <gargaditya08@live.com>
Cc: Ard Biesheuvel <ardb+git@google.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ardb@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, 17 Jul 2024 20:58:30 +0200 [thread overview]
Message-ID: <ZpgUVjjj3naBGtfO@wunner.de> (raw)
In-Reply-To: <MA0P287MB0217E3B4810704C504F13F2CB8A32@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM>
On Wed, Jul 17, 2024 at 04:35:15PM +0000, Aditya Garg wrote:
> For the Macs having a single GPU, in case a person uses an eGPU,
> they still need this apple-set-os quirk for hybrid graphics.
I don't quite follow. You mean the integrated graphics are
disabled by EFI firmware if an eGPU is attached?
This sounds like a bug on Apple's part: The panel can be switched
between integrated graphics and discrete graphics, but an external
display can't be switched between eGPU and iGPU. Is the person
affected using the latest EFI firmware update from Apple?
We need more information before we can devise a way to solve the
issue:
- Exact model name
(I'd be surprised if this affected pre-Haswell models)
- Full dmesg output with command line option "dump_apple_properties"
(EFI drivers provide various properties for Thunderbolt-attached
devices and graphics cards, those could be queried to recognize
the situation causing the issue)
- Full lspci output with and without eGPU attached
Perhaps you can open a bug at bugzilla.kernel.org and attach the
files there.
Thanks,
Lukas
next prev parent reply other threads:[~2024-07-17 18:58 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 [this message]
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
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=ZpgUVjjj3naBGtfO@wunner.de \
--to=lukas@wunner.de \
--cc=ardb+git@google.com \
--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