From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.43; helo=mga05.intel.com; envelope-from=brian.richardson@intel.com; receiver=edk2-devel@lists.01.org Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (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 01D09207E5408 for ; Sun, 13 May 2018 22:21:15 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2018 22:21:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,398,1520924400"; d="scan'208";a="39658105" Received: from orsmsx102.amr.corp.intel.com ([10.22.225.129]) by fmsmga008.fm.intel.com with ESMTP; 13 May 2018 22:21:15 -0700 Received: from orsmsx159.amr.corp.intel.com (10.22.240.24) by ORSMSX102.amr.corp.intel.com (10.22.225.129) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 13 May 2018 22:21:14 -0700 Received: from orsmsx114.amr.corp.intel.com ([169.254.8.24]) by ORSMSX159.amr.corp.intel.com ([169.254.11.190]) with mapi id 14.03.0319.002; Sun, 13 May 2018 22:21:14 -0700 From: "Richardson, Brian" To: Anatol Pomozov CC: "edk2-devel@lists.01.org" Thread-Topic: [edk2] Enabling network interface for Realtek8168 chip Thread-Index: AQHT6sa/cTEoe2g220mMNY/mVJ0xK6QuhNIggACL7oD//574AA== Date: Mon, 14 May 2018 05:21:14 +0000 Message-ID: <80AC2BAA3152784F98F581129E5CF5AFAF216E55@ORSMSX114.amr.corp.intel.com> References: <80AC2BAA3152784F98F581129E5CF5AFAF215B49@ORSMSX114.amr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjUwNzk2MTgtOTNhMC00NWMwLTgyMmUtMDQ0ZmZkODllNjA3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImNcL1E2UGxtSVptajBub3dHR1gyUlI2S1BXWFFreHhGOElOOHdySURZZUJVPSJ9 dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Subject: Re: Enabling network interface for Realtek8168 chip X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 05:21:16 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The driver (.efi file) needs to be included in the EDK II project FDF file = to be properly integrated into the binary firmware image. There is a good e= xample of this in the MinnowBoard Max/Turbot project. https://github.com/tianocore/edk2-platforms/blob/devel-MinnowBoardMax-UDK20= 17/Vlv2TbltDevicePkg/PlatformPkg.fdf Search for "Network Modules" to find the entry where the Realtek & Intel UN= DI drivers are included in the build. Thanks ... br --- Brian Richardson, Senior Technical Marketing Engineer, Intel Software brian.richardson@intel.com -- @intel_brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian= -richardson=20 -----Original Message----- From: edk2-devel On Behalf Of Anatol Pomo= zov Sent: Monday, May 14, 2018 12:03 AM To: Richardson, Brian Cc: edk2-devel@lists.01.org Subject: Re: [edk2] Enabling network interface for Realtek8168 chip Awesome, thank you Brian! On Sun, May 13, 2018 at 7:42 PM, Richardson, Brian wrote: > You can try the UEFI UNDI driver available for download from Realtek's we= bsite: > > http://www.realtek.com/Downloads/downloadsView.aspx?Langid=3D1&PNid=3D13&= P > Fid=3D5&Level=3D5&Conn=3D4&DownTypeID=3D3&GetDown=3Dfa&SortByDesc=3D1 I contacted Zako's device firmware maintainer to add this driver to the fir= mware blob. Meanwhile I am thinking what can I do to try this driver myself (in case if= maintainer is busy and will not make the changes quickly). Is there a way to load this driver programmatically from my UEFI applicatio= n? So I can request and use SimpleNetworkProtocol. Googling did not give me= any clear answer on this topic. And if it does not work, what are other ways for me to enable the network? _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel