public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: devel@edk2.groups.io
Subject: [Patch v5 0/3] Add package level include DSC/FDF in NetworkPkg
Date: Tue,  7 May 2019 22:27:02 +0800	[thread overview]
Message-ID: <20190507142705.20092-1-liming.gao@intel.com> (raw)

v5:
Update Network.fdf.inc to include the missing IScsiDxe
Update NetworkLibs.dsc.inc to add the comments for HttpLib

v4:
Move library instance BaseStackCheckLib to ARM, AARCH64 arch in Patch 1/3
Move PLATFORMX64_ENABLE build flag to package level include DSC file
Correct typo in Patch 3/3

BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1293
BZ 1293 requests to move Network modules from MdeModulePkg to NetworkPkg.
To keep the backword compatiblity, Network package level include DSC/FDF
are introduced to be used in the platform DSC/FDF files. When Network 
modules are moved from MdeModulePkg to NetworkPkg, Network package level 
include DSC/FDF will be updated together. There is no impact on the platform 
DSC/FDF file. 

This patch set is to introduce network package level include DSC/FDF files.
Bases on previous discussion and the existing usage case, build flag will be
used to enable/disable the network features. PCD control feature way can be
discussed later. And, to meet with the different usages, this patch set 
introduces the separate DSC for Defines/Pcds/Libraries/Components (Patch 2)
, and also adds the package level combined DSC to include them all (Patch 3).
If platform wants to use the flexible way to enable Network feature, it can 
use the separate DSCs. If the platform wants to directly enable Network 
feature, it can use the combined package DSC file.

This patch set is to update NetworkPkg only. If there is no objection on this
proposal, the following changes to platform DSC/FDF will be made and sent for
review. By default, the platform DSC/FDF will use the combined DSC/FDF file. 
If the platform owner wants to use the flexible way to enable Network feature,
please reply this mail. 

Feedback from Laszlo, OvmfPkg and ArmVirtPkg platforms to use the
standalone include files from patch #2.


Liming Gao (3):
  NetworkPkg DSC: Add the required ARM library to pass ARM build
  NetworkPkg: Add DSC/FDF include segment files to NetworkPkg.
  NetworkPkg: Add package level include DSC file

 NetworkPkg/Network.dsc.inc           |  40 ++++++++++++
 NetworkPkg/Network.fdf.inc           |  60 ++++++++++++++++++
 NetworkPkg/NetworkComponents.dsc.inc |  61 ++++++++++++++++++
 NetworkPkg/NetworkDefines.dsc.inc    | 118 +++++++++++++++++++++++++++++++++++
 NetworkPkg/NetworkLibs.dsc.inc       |  20 ++++++
 NetworkPkg/NetworkPcds.dsc.inc       |  16 +++++
 NetworkPkg/NetworkPkg.dsc            |  24 +------
 7 files changed, 318 insertions(+), 21 deletions(-)
 create mode 100644 NetworkPkg/Network.dsc.inc
 create mode 100644 NetworkPkg/Network.fdf.inc
 create mode 100644 NetworkPkg/NetworkComponents.dsc.inc
 create mode 100644 NetworkPkg/NetworkDefines.dsc.inc
 create mode 100644 NetworkPkg/NetworkLibs.dsc.inc
 create mode 100644 NetworkPkg/NetworkPcds.dsc.inc

-- 
2.13.0.windows.1


             reply	other threads:[~2019-05-07 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 14:27 Liming Gao [this message]
2019-05-07 14:27 ` [Patch v5 1/3] NetworkPkg DSC: Add the required ARM library to pass ARM build Liming Gao
2019-05-07 14:27 ` [Patch v5 2/3] NetworkPkg: Add DSC/FDF include segment files to NetworkPkg Liming Gao
2019-05-07 14:53   ` [edk2-devel] " Siyuan, Fu
2019-05-07 18:27   ` Laszlo Ersek
2019-05-07 18:37   ` Laszlo Ersek
2019-05-08  0:14     ` Liming Gao
2019-05-14 14:33       ` Laszlo Ersek
2019-05-14 15:03         ` Liming Gao
2019-05-07 14:27 ` [Patch v5 3/3] NetworkPkg: Add package level include DSC file Liming Gao
2019-05-07 14:53   ` [edk2-devel] " Siyuan, Fu

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=20190507142705.20092-1-liming.gao@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