public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Fu Siyuan <siyuan.fu@intel.com>
To: edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Julien Grall <julien.grall@linaro.org>
Subject: [PATCH v3 0/1] Delete TCP, PXE, iSCSI driver in MdeModulePkg.
Date: Tue,  6 Nov 2018 09:24:02 +0800	[thread overview]
Message-ID: <20181106012403.84760-1-siyuan.fu@intel.com> (raw)

V3 Update:
1. Changes for OvmfPkg and Vlv2TbltDevicePkg have been committed so not 
   included in this v3 patch.
2. Remove ArmVirtPkg duplicate library added in v2 patch.

V2 Update:
1. Changes for Nt32Pkg and EmulatorPkg have been committed so not 
   included in this v2 patch.
2. Add missing library instance for NetworkPkg iSCSI driver.
3. The removal of the 3 modules from MdeModulePkg will not be included
   in edk2-stable201811 tag, so not included in this v2 patch.

This patch series is to delete the Tcp4Dxe, UefiPxeBcDxe and IScsi4Dxe
drivers in MdeModulePkg. These drivers will not be maintained and can't
co-work with the dual-stack drivers in NetworkPkg.

People should use below NetworkPkg drivers instead:
  NetworkPkg/IScsiDxe/IScsiDxe.inf
  NetworkPkg/TcpDxe/TcpDxe.inf
  NetworkPkg/UefiPxeBcDxe/UefiPxeBcDxe.inf
These drivers are actively maintained with more bug fixes and new feature
support.

The MdeModulePkg iSCSI driver implements its own Md5.c instead of using
standard crypto API provided by OpenSSL, which is not allowed by edk2
security development guide line. NetworkPkg iSCSI driver doesn't have
this issue and so need to be built with OpenSSL library instance now.
Please add below library instance to your DSC file.
[LibraryClasses.common.UEFI_DRIVER]
  BaseCryptLib|CryptoPkg/Library/BaseCryptLib/BaseCryptLib.inf
  OpensslLib|CryptoPkg/Library/OpensslLib/OpensslLib.inf
  IntrinsicLib|CryptoPkg/Library/IntrinsicLib/IntrinsicLib.inf

Patch 1~5 update edk2 platform DSC/FDF files to use NetworkPkg drivers.
Patch 6 deletes the TCP,PXE,iSCSI driver in MdeModulePkg.
Patch 7 removes some clarification in NetworkPkg drivers since the
related driver has been deleted in Patch 6.

Fu Siyuan (1):
  ArmVirtPkg: Replace obsoleted network drivers from platform DSC/FDF.

Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Julien Grall <julien.grall@linaro.org>

 ArmVirtPkg/ArmVirt.dsc.inc           |  2 --
 ArmVirtPkg/ArmVirtQemu.dsc           | 10 +++-------
 ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 10 +++-------
 ArmVirtPkg/ArmVirtQemuKernel.dsc     | 13 ++++++-------
 4 files changed, 12 insertions(+), 23 deletions(-)

-- 
2.19.1.windows.1



             reply	other threads:[~2018-11-06  1:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  1:24 Fu Siyuan [this message]
2018-11-06  1:24 ` [PATCH v3 1/1] ArmVirtPkg: Replace obsoleted network drivers from platform DSC/FDF Fu Siyuan
2018-11-06 12:32   ` Ard Biesheuvel
2018-11-06 15:24     ` Laszlo Ersek
2018-11-06 16:39       ` Ard Biesheuvel
2018-11-07  0:58         ` Fu, Siyuan
2018-12-14  6:11         ` Fu, Siyuan
2018-12-14  7:22           ` Ard Biesheuvel
2018-11-06 15:18   ` Laszlo Ersek

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=20181106012403.84760-1-siyuan.fu@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