From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [edk2-platform patch 2/7] RDKQemu: Update RDKQemu.dsc to remove unnecessary Network libs
Date: Mon, 10 Jun 2019 11:06:18 +0200 [thread overview]
Message-ID: <CAKv+Gu_cGyG2oAwvXBvKVmCd8hDmSXh5QCSuuTJojdAdtKN+aQ@mail.gmail.com> (raw)
In-Reply-To: <20190528095853.16476-3-liming.gao@intel.com>
On Tue, 28 May 2019 at 12:00, Liming Gao <liming.gao@intel.com> wrote:
>
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
This still does not build. It has lots of other errors, but with those
fixes, we still need to set NETWORK_ALLOW_HTTP_CONNECTIONS to TRUE to
retain the old behavior.
I will follow up with a patch that fixes this platform, no need to resend.
> ---
> Platform/Comcast/RDKQemu/RDKQemu.dsc | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/Platform/Comcast/RDKQemu/RDKQemu.dsc b/Platform/Comcast/RDKQemu/RDKQemu.dsc
> index 64b6699ae7..e73a907891 100644
> --- a/Platform/Comcast/RDKQemu/RDKQemu.dsc
> +++ b/Platform/Comcast/RDKQemu/RDKQemu.dsc
> @@ -33,7 +33,7 @@
> # Network definition
> #
> DEFINE NETWORK_SNP_ENABLE = FALSE
> - DEFINE NETWORK_TLS_ENABLE = FALSE
> + DEFINE NETWORK_TLS_ENABLE = TRUE
> DEFINE NETWORK_IP6_ENABLE = FALSE
> DEFINE NETWORK_HTTP_BOOT_ENABLE = TRUE
>
> @@ -65,9 +65,6 @@
> PciSegmentLib|MdePkg/Library/BasePciSegmentLibPci/BasePciSegmentLibPci.inf
> PciHostBridgeLib|ArmVirtPkg/Library/FdtPciHostBridgeLib/FdtPciHostBridgeLib.inf
> RdkBootManagerLib|Platform/Comcast/Library/RdkBootManagerLib/RdkBootManagerLib.inf
> -!if $(HTTP_BOOT_ENABLE) == TRUE
> - HttpLib|MdeModulePkg/Library/DxeHttpLib/DxeHttpLib.inf
> -!endif
>
> [LibraryClasses.common.PEIM]
> ArmVirtMemInfoLib|ArmVirtPkg/Library/QemuVirtMemInfoLib/QemuVirtMemInfoPeiLib.inf
> --
> 2.13.0.windows.1
>
>
>
>
next prev parent reply other threads:[~2019-06-10 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 9:58 [edk2-platform patch 0/7] Clean up Platform DSC/FDF to refer to NetworkPkg Liming Gao
2019-05-28 9:58 ` [edk2-platform patch 1/7] BeagleBoardPkg: Update BeagleBoardPkg.dsc to remove unnecessary Network libs Liming Gao
2019-06-10 8:03 ` Ard Biesheuvel
2019-05-28 9:58 ` [edk2-platform patch 2/7] RDKQemu: Update RDKQemu.dsc " Liming Gao
2019-06-10 9:06 ` Ard Biesheuvel [this message]
2019-05-28 9:58 ` [edk2-platform patch 3/7] Hisilicon: Update D06.dsc " Liming Gao
2019-06-10 10:49 ` Ard Biesheuvel
2019-05-28 9:58 ` [edk2-platform patch 4/7] QuarkPlatform: Update Quark dsc " Liming Gao
2019-05-28 9:58 ` [edk2-platform patch 5/7] Vlv2TbltDevicePkg: Update Platform " Liming Gao
2019-05-28 10:04 ` [edk2-devel] " Sun, Zailiang
2019-05-28 9:58 ` [edk2-platform patch 6/7] RaspberryPi: Update RPi3 DSC/FDF to refer to Network package segment files Liming Gao
2019-05-28 9:58 ` [edk2-platform patch 7/7] SoftIron: Update Overdrive1000Board.dsc to refer to new Network module path Liming Gao
2019-06-10 10:41 ` Ard Biesheuvel
2019-05-28 10:05 ` [edk2-devel] [edk2-platform patch 0/7] Clean up Platform DSC/FDF to refer to NetworkPkg Ard Biesheuvel
2019-05-28 11:03 ` Liming Gao
2019-05-28 11:11 ` Ard Biesheuvel
2019-05-28 11:44 ` 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=CAKv+Gu_cGyG2oAwvXBvKVmCd8hDmSXh5QCSuuTJojdAdtKN+aQ@mail.gmail.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