From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"leif@nuviainc.com" <leif@nuviainc.com>
Cc: "Tian, Hot" <hot.tian@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
"Kirkendall, Garrett" <garrett.kirkendall@amd.com>,
"Lendacky, Thomas" <thomas.lendacky@amd.com>,
"thomas.abraham@arm.com" <thomas.abraham@arm.com>,
"Frank.Orr@dell.com" <Frank.Orr@dell.com>,
"Jim Dailey" <jim.dailey@dell.com>,
Abner Chang <abner.chang@hpe.com>,
"Wang, Sunny (HPS SW)" <sunnywang@hpe.com>,
Daniel Schaefer <daniel.schaefer@hpe.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Tim Lewis <tim.lewis@insyde.com>,
"Kevin@Insyde" <kevin.davis@insyde.com>,
"Felix Polyudov" <felixp@ami.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Oram, Isaac W" <isaac.w.oram@intel.com>,
"Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [edk2-rfc] [RFC] Request to move MinPlatformPkg out of the Intel folder
Date: Mon, 5 Oct 2020 20:11:33 +0000 [thread overview]
Message-ID: <MWHPR1101MB21604F10741EF5244826CED0CD0C0@MWHPR1101MB2160.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201004220007.GO5623@vanye>
Hey Leif,
On 10/4/20, 3:00 PM, Leif Lindholm <leif@nuviainc.com> wrote:
>
> On Sun, Oct 04, 2020 at 20:46:50 +0000, Desimone, Nathaniel L wrote:
> > Hey Hot,
> >
> > On 10/1/20, 9:20 PM, Tian, Hot <hot.tian@intel.com> wrote:
> > >
> > > Why not move to edk2 repo?
> >
> > Edk2 would be a good place as well.
>
> If it is being used by any external consumers, then yes edk2 makes perfect
> sense.
>
> It might still make sense to start prototyping that usage in a vendor-neutral
> section of edk2-platforms.
It is actually seeing a pretty large amount of external consumption right now. To my knowledge, every IBV and most OEMs depend on MinPlatformPkg for Tiger Lake UEFI firmware implementations. Given the interest we have seen here for non-Intel MinPlatform firmware, I believe that edk2 is likely the best place for it.
Thanks,
Nate
next prev parent reply other threads:[~2020-10-06 2:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 23:17 [RFC] Request to move MinPlatformPkg out of the Intel folder Nate DeSimone
2020-10-01 4:04 ` Abner Chang
2020-10-01 6:54 ` Laszlo Ersek
2020-10-01 23:27 ` [edk2-devel] " Nate DeSimone
2020-10-01 7:43 ` Wim Vervoorn
2020-10-01 8:00 ` [edk2-devel] " christian.walter
2020-10-01 11:24 ` Kirkendall, Garrett
2020-10-01 11:52 ` Leif Lindholm
2020-10-01 23:20 ` [edk2-rfc] " Nate DeSimone
2020-10-01 23:26 ` Leif Lindholm
2020-10-02 4:19 ` [edk2-devel] " Hot Tian
2020-10-04 20:46 ` Nate DeSimone
2020-10-04 22:00 ` Leif Lindholm
2020-10-05 20:11 ` Nate DeSimone [this message]
2020-10-03 3:36 ` [edk2-devel] " Sean
2020-10-04 21:02 ` Nate DeSimone
2020-10-05 19:35 ` Bret Barkelew
2020-10-05 20:18 ` [edk2-rfc] " Nate DeSimone
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-list 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=MWHPR1101MB21604F10741EF5244826CED0CD0C0@MWHPR1101MB2160.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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