From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rebecca@bluestop.org>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=96.73.9.1; helo=muon.bluestop.org;
 envelope-from=rebecca@bluestop.org; receiver=edk2-devel@lists.01.org 
Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 7FD5E202E53B7
 for <edk2-devel@lists.01.org>; Tue, 12 Feb 2019 20:28:17 -0800 (PST)
Received: from muon.bluestop.org (localhost [127.0.0.1])
 by muon.bluestop.org (Postfix) with ESMTP id 81E53DD77;
 Tue, 12 Feb 2019 21:29:11 -0700 (MST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluestop.org; s=mail;
 t=1550032151; bh=JcTdOmQ8KASV/XOtnpWUUkD5l9HQhwMqCeUwKiHRbdo=;
 h=Date:From:To:Cc:In-Reply-To:References:Subject:From;
 b=LGuyfFY2XlQjzBbLOOOF8KH36glQyOZUHl6wpQXt6meZasK6DsPX6qFfz+kOHp0wx
 gJ1/HA8uQo/izaIu/twtGAARN1uQo79ThHnBDXe/ZcGuRakA5uHih9De6u5Q+kBFNp
 3AXDayCExqGQpPzowrg4DcEoj3CKNlzsedOaIOHQ=
Received: from muon.bluestop.org ([127.0.0.1])
 by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id MpfzmFLqEOfz; Tue, 12 Feb 2019 21:29:10 -0700 (MST)
Received: from macbex.int.bluestop.org.mail (gw.bluestop.org [96.73.9.3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by muon.bluestop.org (Postfix) with ESMTPSA;
 Tue, 12 Feb 2019 21:29:10 -0700 (MST)
Date: Tue, 12 Feb 2019 21:28:15 -0700
From: Rebecca Cran <rebecca@bluestop.org>
To: Laszlo Ersek <lersek@redhat.com>, Rebecca Cran via edk2-devel
 <edk2-devel@lists.01.org>
Cc: edk2-devel@lists.01.org
Message-ID: <etPan.5c639cdf.67e2aa78.20ad@bluestop.org>
In-Reply-To: <2834820.0P3pStmDMi@photon.int.bluestop.org>
References: <4656579.YNO7O01DYZ@photon.int.bluestop.org>
 <1568584.MsCH1bHPGx@photon.int.bluestop.org>
 <059fccc8-3ab5-057b-008a-efbeb30438a9@redhat.com>
 <2834820.0P3pStmDMi@photon.int.bluestop.org>
MIME-Version: 1.0
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: OVMF and TCP4, HTTP protocols
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 04:28:17 -0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On =46ebruary 6, 2019 at 4:08:03 PM, Rebecca Cran via edk2-devel (edk2-de=
vel=40lists.01.org) wrote:

Oh, that makes sense=21 Thanks, after disabling the existing code that wa=
s=C2=A0
opening SNP exclusively, things started working much better.=C2=A0


I have a follow-up question. After opening the E=46I=5FSIMPLE=5FNETWORK p=
rotocol exclusively, should code be able to later call gBS->CloseProtocol=
 on the handle and subsequently start using TCP/HTTP=3F=C2=A0

=46rom what I=E2=80=99ve seen, closing the protocol (I=E2=80=99m also cal=
ling net->Shutdown(), and the CloseProtocol succeeds) has no effect and t=
he TCP and HTTP protocols still can=E2=80=99t be found/used.



=E2=80=94=C2=A0

Rebecca Cran