From: Aditya Garg <gargaditya08@live.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Orlando Chamberlain <orlandoch.dev@gmail.com>,
"lukas@wunner.de" <lukas@wunner.de>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"kekrby@gmail.com" <kekrby@gmail.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sharpenedblade@proton.me" <sharpenedblade@proton.me>
Subject: Re: [PATCH v3 0/2] efi/x86: Call set_os() protocol on dual GPU Macs
Date: Mon, 29 Jul 2024 07:46:20 +0000 [thread overview]
Message-ID: <MA0P287MB02176046C8D80AF7CB47ED9DB8B72@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAMj1kXHw0_MicBifz0FdLCOcjjD73AJcM-dyG1J6Ah=BjuQNcw@mail.gmail.com>
> Thanks, this seems useful.
>
> Does this mean we can drop the type1 product name list, and just look
> for 'iBridge' in the type0 version string? Or does that list contain
> non-T2 hardware as well?
MacBookPro11,3
MacBookPro11,5
MacBookPro13,3
MacBookPro14,3
These are non T2 Macs that were in the previous list
prev parent reply other threads:[~2024-07-29 7:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:09 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
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 [this message]
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=MA0P287MB02176046C8D80AF7CB47ED9DB8B72@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM \
--to=gargaditya08@live.com \
--cc=ardb@kernel.org \
--cc=hdegoede@redhat.com \
--cc=kekrby@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--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
all inboxes | Powered by JetHome®