From: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms][ 1/3] Update Platform/Intel/Readme.md to specify master instead of devel-MinPlatform branch
Date: Mon, 13 May 2019 19:07:21 +0000 [thread overview]
Message-ID: <49AB4ACB9627B8468F29D589A27B74558893A2E5@ORSMSX121.amr.corp.intel.com> (raw)
In-Reply-To: <20190513140910.17452-2-liming.gao@intel.com>
Reviewed-by: Michael Kubacki <michael.a.kubacki@intel.com>
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Liming Gao
> Sent: Monday, May 13, 2019 7:09 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [edk2-platforms][ 1/3] Update
> Platform/Intel/Readme.md to specify master instead of devel-MinPlatform
> branch
>
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
> Platform/Intel/Readme.md | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Platform/Intel/Readme.md b/Platform/Intel/Readme.md index
> fbf735173f..1da5d0ad29 100644
> --- a/Platform/Intel/Readme.md
> +++ b/Platform/Intel/Readme.md
> @@ -8,7 +8,7 @@ Package maintainers for the Minimum Platform projects
> are listed in Maintainers.
> ## Overview
> The key elements of the architecture are organized into a staged boot
> approach where each stage has requirements and functionality for specific
> use cases. The generic control flow through the boot process is implemented
> in the -[`MinPlatformPkg`](https://github.com/tianocore/edk2-
> platforms/tree/devel-MinPlatform/Platform/Intel/MinPlatformPkg).
> +[`MinPlatformPkg`](https://github.com/tianocore/edk2-
> platforms/tree/master/Platform/Intel/MinPlatformPkg).
> The generic nature of the tasks performed in MinPlatformPkg lends to reuse
> across all Intel platforms with no source modification. Details for any
> particular board are made accessible to the MinPlatformPkg through a well-
> defined statically linked board API. A complete platform solution then
> consists of the MinPlatformPkg and a compatible board @@ -16,13 +16,13
> @@ package.
>
> ## Board Naming Convention
> The board packages supported by Intel follow the naming convention
> \<xxx\>OpenBoardPkg where xxx refers to the -encompassing platform
> name for a particular platform generation. For example, the
> [`KabylakeOpenBoardPkg`](https://github.com/tianocore/edk2-
> platforms/tree/devel-MinPlatform/Platform/Intel/KabylakeOpenBoardPkg)
> contains the
> +encompassing platform name for a particular platform generation. For
> +example, the
> +[`KabylakeOpenBoardPkg`](https://github.com/tianocore/edk2-
> platforms/tr
> +ee/master/Platform/Intel/KabylakeOpenBoardPkg) contains the
> board code for Intel Kaby Lake reference systems. Intel uses the moniker
> "OpenBoardPkg" to indicate that this package is the open source board
> code. A closed source counterpart may exist which simply uses "BoardPkg".
> Both directly use the MinPlatformPkg from edk2-platforms.
>
> ## Stage Selection
> -Stage selection is controlled via the PCD
> `gMinPlatformPkgTokenSpaceGuid.PcdBootStage` in
> [`MinPlatformPkg.dec`](https://github.com/tianocore/edk2-
> platforms/blob/devel-
> MinPlatform/Platform/Intel/MinPlatformPkg/MinPlatformPkg.dec).
> +Stage selection is controlled via the PCD
> `gMinPlatformPkgTokenSpaceGuid.PcdBootStage` in
> [`MinPlatformPkg.dec`](https://github.com/tianocore/edk2-
> platforms/tree/master/Platform/Intel/MinPlatformPkg/MinPlatformPkg.dec)
> .
> The stage should be configured in the board package DSC file to the
> appropriate value. For example, a board may disable all advanced features
> by setting this value to 4 instead of 6. This may be used to improve boot time
> for a particular use case. Decrementing the stage can also be used for debug
> since only the actions required for that stage objective @@ -46,8 +46,8 @@
> A UEFI firmware implementation using MinPlatformPkg is constructed using
> the fol |------------------------------------|
> | [EDK II](https://github.com/tianocore/edk2)
> |
> | [Intel(r) FSP](https://github.com/IntelFsp/FSP)
> |
> -| [Minimum Platform
> (`MinPlatformPkg`)](https://github.com/tianocore/edk2-
> platforms/tree/devel-MinPlatform/Platform/Intel/MinPlatformPkg)
> |
> -| [Board Support
> -| (\<xxx\>OpenBoardPkg)](https://github.com/tianocore/edk2-platforms/tr
> -| ee/devel-MinPlatform/Platform/Intel) |
> +| [Minimum Platform
> (`MinPlatformPkg`)](https://github.com/tianocore/edk2-
> platforms/tree/master/Platform/Intel/MinPlatformPkg) |
> +| [Board Support
> +| (\<xxx\>OpenBoardPkg)](https://github.com/tianocore/edk2-platforms/tr
> +| ee/master/Platform/Intel) |
>
>
> ## Board Support
> @@ -95,7 +95,7 @@ return back to the minimum platform caller.
> * ``git clone https://github.com/tianocore/edk2.git``
>
> * edk2-platforms repository
> - * ``git clone https://github.com/tianocore/edk2-platforms.git -b devel-
> MinPlatform``
> + * ``git clone https://github.com/tianocore/edk2-platforms.git``
>
> * edk2-non-osi repository
> * ``git clone https://github.com/tianocore/edk2-non-osi.git -b devel-
> MinPlatform``
> --
> 2.13.0.windows.1
>
>
>
next prev parent reply other threads:[~2019-05-13 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 14:09 [edk2-platforms][0/3] Update Readme and Maintainers.txt Liming Gao
2019-05-13 14:09 ` [edk2-platforms][ 1/3] Update Platform/Intel/Readme.md to specify master instead of devel-MinPlatform branch Liming Gao
2019-05-13 19:07 ` Kubacki, Michael A [this message]
2019-05-13 14:09 ` [edk2-platforms][ 2/3] Merge Maintainers.txt in Platform\Intel and Silicon\Intel to root directory Liming Gao
2019-05-13 19:07 ` [edk2-devel] " Kubacki, Michael A
2019-05-13 14:09 ` [edk2-platforms][ 3/3] Update Readme.md to list Intel MinPlatform systems Liming Gao
2019-05-15 15:58 ` [edk2-devel] " Kubacki, Michael A
2019-05-16 0:03 ` Liming Gao
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=49AB4ACB9627B8468F29D589A27B74558893A2E5@ORSMSX121.amr.corp.intel.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