From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (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 0616821B02B8F for ; Thu, 29 Jun 2017 18:19:30 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 18:21:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,283,1496127600"; d="scan'208";a="1166417599" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga001.fm.intel.com with ESMTP; 29 Jun 2017 18:21:02 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 29 Jun 2017 18:20:42 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by shsmsx102.ccr.corp.intel.com ([169.254.2.146]) with mapi id 14.03.0319.002; Fri, 30 Jun 2017 09:20:39 +0800 From: "Wu, Jiaxin" To: Laszlo Ersek , edk2-devel-01 CC: "Justen, Jordan L" Thread-Topic: [PATCH 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil v.22 Thread-Index: AQHS8FrhUsiQbV/u2UKvPkenHATDZqI8m/XA Date: Fri, 30 Jun 2017 01:20:38 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B7274162E0D07@SHSMSX103.ccr.corp.intel.com> References: <20170628220645.26413-1-lersek@redhat.com> <20170628220645.26413-3-lersek@redhat.com> In-Reply-To: <20170628220645.26413-3-lersek@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiN2NiYjQyMzYtNzg1Mi00MWE5LWI0Y2UtNmRlN2UyNGFiYWVlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNi41LjkuMyIsIlRydXN0ZWRMYWJlbEhhc2giOiJtUkJMZ3BtT0ZmY2FZc1hnODQ4Q1JyMytnZ3hcL0VYZmkxNHdYMHRVb3dzYz0ifQ== x-ctpclassification: CTP_PUBLIC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: [PATCH 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil v.22 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jun 2017 01:19:30 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable After patch with "[PATCH 1/2] disable build-time relocation for DXEFV modul= es", I can pass the platform build, then HTTP boot feature has been verifie= d. Tested-by: Wu Jiaxin Reviewed-by: Wu Jiaxin Thanks, Jiaxin > -----Original Message----- > From: Laszlo Ersek [mailto:lersek@redhat.com] > Sent: Thursday, June 29, 2017 6:07 AM > To: edk2-devel-01 > Cc: Wu, Jiaxin ; Justen, Jordan L > > Subject: [PATCH 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI > v.07 to BootUtil v.22 >=20 > Jiaxin reports that the OvmfPkg/README instructions for downloading the > Intel PROEFI drivers, and the filenames in OvmfPkg/OvmfPkg*.fdf for > incorporating the same in the OVMF binaries, are no longer up to date; th= e > download link has stopped working. >=20 > Additionally, the IA32 driver binary is no more distributed by Intel. >=20 > Update OvmfPkg/README with new download instructions, and adapt the > OVMF > FDF files. >=20 > With this driver in use for QEMU's e1000 NIC, the DH shell command prints= , > as Controller Name, "Intel(R) PRO/1000 MT Network Connection". I > successfully tested DHCP and ping from the UEFI shell. >=20 > Cc: Jiaxin Wu > Cc: Jordan Justen > Reported-by: Jiaxin Wu > Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3D613 > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Laszlo Ersek > --- > OvmfPkg/OvmfPkgIa32.fdf | 5 ---- > OvmfPkg/OvmfPkgIa32X64.fdf | 2 +- > OvmfPkg/OvmfPkgX64.fdf | 2 +- > OvmfPkg/README | 31 +++++++++++++------- > 4 files changed, 23 insertions(+), 17 deletions(-) >=20 > diff --git a/OvmfPkg/OvmfPkgIa32.fdf b/OvmfPkg/OvmfPkgIa32.fdf > index 859457e9aae5..cd91bc03a683 100644 > --- a/OvmfPkg/OvmfPkgIa32.fdf > +++ b/OvmfPkg/OvmfPkgIa32.fdf > @@ -294,11 +294,6 @@ [FV.DXEFV] > # > # Network modules > # > -!if $(E1000_ENABLE) > - FILE DRIVER =3D 5D695E11-9B3F-4b83-B25F-4A8D5D69BE07 { > - SECTION PE32 =3D Intel3.5/EFI32/E3507E2.EFI > - } > -!endif > INF MdeModulePkg/Universal/Network/SnpDxe/SnpDxe.inf > INF MdeModulePkg/Universal/Network/DpcDxe/DpcDxe.inf > INF MdeModulePkg/Universal/Network/MnpDxe/MnpDxe.inf > diff --git a/OvmfPkg/OvmfPkgIa32X64.fdf b/OvmfPkg/OvmfPkgIa32X64.fdf > index 2a0ed8313786..fae82709aee1 100644 > --- a/OvmfPkg/OvmfPkgIa32X64.fdf > +++ b/OvmfPkg/OvmfPkgIa32X64.fdf > @@ -296,7 +296,7 @@ [FV.DXEFV] > # > !if $(E1000_ENABLE) > FILE DRIVER =3D 5D695E11-9B3F-4b83-B25F-4A8D5D69BE07 { > - SECTION PE32 =3D Intel3.5/EFIX64/E3507X2.EFI > + SECTION PE32 =3D Intel3.5/EFIX64/E3522X2.EFI > } > !endif > INF MdeModulePkg/Universal/Network/SnpDxe/SnpDxe.inf > diff --git a/OvmfPkg/OvmfPkgX64.fdf b/OvmfPkg/OvmfPkgX64.fdf > index ca61fa125795..4da0b19b94cf 100644 > --- a/OvmfPkg/OvmfPkgX64.fdf > +++ b/OvmfPkg/OvmfPkgX64.fdf > @@ -296,7 +296,7 @@ [FV.DXEFV] > # > !if $(E1000_ENABLE) > FILE DRIVER =3D 5D695E11-9B3F-4b83-B25F-4A8D5D69BE07 { > - SECTION PE32 =3D Intel3.5/EFIX64/E3507X2.EFI > + SECTION PE32 =3D Intel3.5/EFIX64/E3522X2.EFI > } > !endif > INF MdeModulePkg/Universal/Network/SnpDxe/SnpDxe.inf > diff --git a/OvmfPkg/README b/OvmfPkg/README > index 33ff9432bb3e..00fb71848200 100644 > --- a/OvmfPkg/README > +++ b/OvmfPkg/README > @@ -224,24 +224,35 @@ longer.) > basic virtio-net driver, located in OvmfPkg/VirtioNetDxe. >=20 > * Also independently of the iPXE NIC drivers, Intel's proprietary E1000 = NIC > - driver (PROEFI) can be embedded in the OVMF image at build time: > + driver (from the BootUtil distribution) can be embedded in the OVMF > image at > + build time: >=20 > - - Download UEFI drivers for the e1000 NIC > - - > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=3DY&DwnldID=3D17515& > lang=3Deng > - - Install the drivers into a directory called Intel3.5 in your WORKS= PACE. > + - Download BootUtil: > + - Navigate to > + https://downloadcenter.intel.com/download/19186/Ethernet-Intel- > Ethernet-Connections-Boot-Utility-Preboot-Images-and-EFI-Drivers > + - Click the download link for "PREBOOT.EXE". > + - Accept the Intel Software License Agreement that appears. > + - Unzip "PREBOOT.EXE" into a separate directory (this works with the > + "unzip" utility on platforms different from Windows as well). > + - Copy the "APPS/EFI/EFIx64/E3522X2.EFI" driver binary to > + "Intel3.5/EFIX64/E3522X2.EFI" in your WORKSPACE. > + - Intel have stopped distributing an IA32 driver binary (which used = to > + match the filename pattern "E35??E2.EFI"), thus this method will o= nly > + work for the IA32X64 and X64 builds of OVMF. >=20 > - Include the driver in OVMF during the build: > - - Add "-D E1000_ENABLE" to your build command, > + - Add "-D E1000_ENABLE" to your build command (only when building > + "OvmfPkg/OvmfPkgIa32X64.dsc" or "OvmfPkg/OvmfPkgX64.dsc"). > - For example: "build -D E1000_ENABLE". >=20 > * When a matching iPXE driver is configured for a NIC as described above= , it > takes priority over other drivers that could possibly drive the card t= oo: >=20 > - | e1000 ne2k_pci pcnet rtl8139 virtio-net-pci > - -------------+------------------------------------------------ > - iPXE | x x x x x > - VirtioNetDxe | x > - Intel PROEFI | x > + | e1000 ne2k_pci pcnet rtl8139 virtio-net-p= ci > + ---------------------+----------------------------------------------= -- > + iPXE | x x x x x > + VirtioNetDxe | x > + Intel BootUtil (X64) | x >=20 > =3D=3D=3D OVMF Flash Layout =3D=3D=3D >=20 > -- > 2.13.1.3.g8be5a757fa67