From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 2FCCD211C831F for ; Wed, 6 Feb 2019 11:05:10 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D95123C2CCF; Wed, 6 Feb 2019 19:05:09 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-4.rdu2.redhat.com [10.10.120.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3384B1850F; Wed, 6 Feb 2019 19:05:09 +0000 (UTC) To: Rebecca Cran Cc: edk2-devel@lists.01.org References: <4656579.YNO7O01DYZ@photon.int.bluestop.org> <8a2008b8-3d5b-4c8e-8f92-32001dbc90ea@redhat.com> <1568584.MsCH1bHPGx@photon.int.bluestop.org> From: Laszlo Ersek Message-ID: <059fccc8-3ab5-057b-008a-efbeb30438a9@redhat.com> Date: Wed, 6 Feb 2019 20:05:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1568584.MsCH1bHPGx@photon.int.bluestop.org> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Wed, 06 Feb 2019 19:05:09 +0000 (UTC) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2019 19:05:11 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 02/06/19 18:44, Rebecca Cran wrote: > On Wednesday, 6 February 2019 09:36:43 MST Laszlo Ersek wrote: > >> please refer to the HTTP_BOOT_ENABLE define in the OVMF DSC files; the >> default value is FALSE. >> >> If you'd like HTTP over IPv6, then please pass -D NETWORK_IP6_ENABLE on >> the "build" cmdline as well. > > Thanks. I'm already building with HTTP_BOOT_ENABLE though, and successfully > fetching loader.efi from the web server. However once loader.efi runs, my code > can't find the HTTP or TCPv4 protocols. > >>> Start HTTP Boot over IPv4..... > Station IP address is 192.168.0.119 > > URI: http://192.168.0.1/boot/loader.efi > File Size: 480256 Bytes > Downloading...100% > Is "loader.efi" opaque, or do we know what it does? For example, if it opens SNP with BY_DRIVER|EXCLUSIVE attributes, then everything on top will be disconnected. (I don't understand clearly if "loader.efi" is your own code in fact.) Here's an idea: (1) Build "loader.efi" and code "around" it with OvmfPkg/Library/PlatformDebugLibIoPort/PlatformDebugLibIoPort.inf as the DebugLib instance. Then debug messages from the application and the platform firmware will be nicely intermixed on the QEMU debug port. (2) Add a DEBUG_INFO message to CoreUninstallProtocolInterface() [MdeModulePkg/Core/Dxe/Hand/Handle.c], logging the fact and the protocol GUID. (3) Search the log for installation & uninstallation of the GUID BDC8E6AF-D9BC-4379-A72A-E0C4E75DAE1C (EFI_HTTP_SERVICE_BINDING_PROTOCOL). Perhaps you can correlate those log entries with other events. Thanks Laszlo