From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: devel@edk2.groups.io, michael.a.kubacki@intel.com
Cc: Liming Gao <liming.gao@intel.com>, Andrew Fish <afish@apple.com>,
Laszlo Ersek <lersek@redhat.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [edk2-devel] [edk2-platforms] [RFC] Migrate devel-MinPlatform branch to master branch
Date: Thu, 2 May 2019 16:04:27 +0100 [thread overview]
Message-ID: <20190502150427.ihzom3w4fvjpxopk@bivouac.eciton.net> (raw)
In-Reply-To: <49AB4ACB9627B8468F29D589A27B7455888CA32F@ORSMSX122.amr.corp.intel.com>
Hi Michael,
On Thu, Apr 18, 2019 at 09:11:38PM +0000, Kubacki, Michael A wrote:
> Hello,
>
> This RFC proposes moving the content on the devel-MinPlatform branch
> in the edk2-platforms repository to the master branch in the
> edk2-platforms repository.
>
> The devel-MinPlatform branch has been used for the initial development
> of an EDK II based platform design referred to as "Minimum Platform".
> This design is intended to provide a structured approach to introducing
> Intel platform code into open source in a consistent manner.
>
> For more information about the EDK II Minimum Platform, please refer to
> the Readme.md in devel-MinPlatform.
> https://github.com/tianocore/edk2-platforms/blob/devel-MinPlatform/ReadMe.md
>
> The following packages would be added in Platform/Intel:
> * Generic packages:
> * AdvancedFeaturePkg
> * MinPlatformPkg
First a generic comment with some examples:
Both of these include non-architecture-specific components that could
be useful to have more generally available.
Certainly AdvancedFeaturePkg/Smbios/ and AcpiDebug look like something
of a generic nature rather than Intel-platform specific.
And Platform/Intel/MinPlatformPkg/Library/CompressLib/CompressLib.c
appears to have nearly only whitespace differences compared to edk2
ShellPkg/Library/UefiShellDebug1CommandsLib/Compress.c.
(With edk2 already having 3 additional quite similar files in
BaseTools/Source/C/Common/EfiCompress.c
BaseTools/Source/C/Common/TianoCompress.c
BaseTools/Source/C/TianoCompress/TianoCompress.c)
Secondly - edk2 has recently transitioned to bsd+patents license, and
it would make sense if edk2-platforms did the same. Do we want to do
that before or after this addition?
Finally, what should we do for Maintainers.txt?
Best Regards,
Leif
> * Board-specific packages:
> * ClevoOpenBoardPkg
> * KabylakeOpenBoardPkg
> * PurleyOpenBoardPkg
>
> The following packages would be added in Silicon/Intel:
> * KabylakeSiliconPkg
> * LewisburgPkg
> * PurleyRcPkg
> * PurleySktPkg
>
> The following growth is expected over time:
> * Platform/Intel - Additional board packages for Intel reference boards
> including support for some pre-existing product releases
> * AdvancedFeaturePkg - Additional modular features capable of being used
> in board packages
> * Silicon/Intel - Additional silicon packages roughly keeping 1:1 parity
> with board packages
>
> We hope the content will enable others to add new board packages and advanced
> features over time.
>
> The result of the change is available here for reference:
> https://github.com/lgao4/edk2-platforms
>
> Regards,
> Michael
>
>
>
next prev parent reply other threads:[~2019-05-02 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 21:11 [edk2-platforms] [RFC] Migrate devel-MinPlatform branch to master branch Kubacki, Michael A
2019-04-24 7:22 ` Liming Gao
2019-04-24 17:24 ` Kubacki, Michael A
2019-05-02 15:04 ` Leif Lindholm [this message]
2019-05-02 21:15 ` [edk2-devel] " Kubacki, Michael A
2019-05-04 0:32 ` Kubacki, Michael A
2019-05-06 8:22 ` Liming Gao
2019-05-07 2:19 ` Kubacki, Michael A
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=20190502150427.ihzom3w4fvjpxopk@bivouac.eciton.net \
--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