From: Lukas Wunner <lukas@wunner.de>
To: Orlando Chamberlain <orlandoch.dev@gmail.com>
Cc: ardb@kernel.org, gargaditya08@live.com, hdegoede@redhat.com,
kekrby@gmail.com, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] efi: libstub: add support for the apple_set_os protocol
Date: Mon, 1 Jul 2024 15:44:54 +0200 [thread overview]
Message-ID: <ZoKy1jeLC-FRLJgr@wunner.de> (raw)
In-Reply-To: <20240701231452.3d547e7f@redecorated-mbp>
On Mon, Jul 01, 2024 at 11:14:52PM +1000, Orlando Chamberlain wrote:
> > FWIW, there would be only 6 models to match if this needs to be
> > constrained to ones with dual GPUs:
> >
> > MacBookPro11,3
> > MacBookPro11,5
> > MacBookPro13,3
> > MacBookPro14,3
> > MacBookPro15,1
> > MacBookPro16,1
>
> I know that at least these two also need it:
> MacBookPro16,4
> MacBookPro15,3
Ah okay, thanks. I went by the list in Wikipedia, disappointing
that it apparently wasn't updated with those final T2 models:
https://en.wikipedia.org/wiki/MacBook_Pro_(Intel-based)
> I think there could be more older ones too. Apple has a list of
> MacBookPros [0], but I don't know how many of the older models that
> list 2 gpus on their "Tech Specs" pages need apple-set-os.
No, Bruno Bierbaumer's page lists the MacBookPro11,3 and 11,5
as the first models that need apple_set_os:
https://github.com/0xbb/gpu-switch
I'm still using a MacBookPro9,1 (last pre-retina) on a daily basis
and apple_set_os isn't needed there. Neither on the MacBookPro10,1
(first retina). Both were introduced mid 2012.
> The original apple-set-os code was posted to the GRUB mailing list in
> December 2013 [1] so maybe it was in 2013 that new dual GPU Macbooks
> started needing apple-set-os?
Yes, Haswell generation introduced Oct 2013 was the first one that
needed it.
Thanks,
Lukas
next prev parent reply other threads:[~2024-07-01 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 19:24 [PATCH v2] efi: libstub: add support for the apple_set_os protocol Aditya Garg
2024-07-01 4:45 ` Orlando Chamberlain
2024-07-01 5:11 ` Ard Biesheuvel
2024-07-01 5:34 ` Lukas Wunner
2024-07-01 5:38 ` Ard Biesheuvel
2024-07-01 5:50 ` Lukas Wunner
2024-07-01 5:56 ` Ard Biesheuvel
2024-07-01 6:41 ` Lukas Wunner
2024-07-01 7:30 ` Ard Biesheuvel
2024-07-01 7:44 ` Lukas Wunner
2024-07-01 7:49 ` Lukas Wunner
2024-07-01 7:51 ` Ard Biesheuvel
2024-07-01 7:53 ` Aditya Garg
2024-07-01 8:02 ` Aditya Garg
2024-07-01 8:14 ` Lukas Wunner
2024-07-01 9:10 ` Aditya Garg
2024-07-01 10:40 ` Aditya Garg
2024-07-01 7:35 ` Lukas Wunner
2024-07-01 13:14 ` Orlando Chamberlain
2024-07-01 13:44 ` Lukas Wunner [this message]
2024-07-01 6:52 ` 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=ZoKy1jeLC-FRLJgr@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 \
/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