From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id F1298D806D5 for ; Wed, 20 Dec 2023 03:46:06 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=ZOXFVtfXYKYNLCRLhaNymCAzxU/RxvpWKRRgL17g+uo=; c=relaxed/simple; d=groups.io; h=ARC-Seal:ARC-Message-Signature:ARC-Authentication-Results:From:To:CC:Subject:Thread-Topic:Thread-Index:Date:Message-ID:References:In-Reply-To:Accept-Language:MIME-Version:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Language:Content-Type; s=20140610; t=1703043965; v=1; b=TCBMcx6F7IuBKuwRjgWbTFgeUK9NND3qSRGaPfYRTfy43hQrUaWGXxgnFttcq0m/i/klHgP1 4CaH0p/DcQL38T7sln+a3Dh6Fjs93JNsKgIKz3YpxtkzztmL6/DvrAFcwo7pjDn7Rjeuzh2Ywws p+qeu4Cdj6VNOIjXwMB6xAVI= X-Received: by 127.0.0.2 with SMTP id vaW0YY7687511xmXVqGrUKQ5; Tue, 19 Dec 2023 19:46:05 -0800 X-Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) by mx.groups.io with SMTP id smtpd.web10.14536.1703043964111544755 for ; Tue, 19 Dec 2023 19:46:04 -0800 X-IronPort-AV: E=McAfee;i="6600,9927,10929"; a="2584334" X-IronPort-AV: E=Sophos;i="6.04,290,1695711600"; d="scan'208,217";a="2584334" X-Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Dec 2023 19:46:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10929"; a="846571380" X-IronPort-AV: E=Sophos;i="6.04,290,1695711600"; d="scan'208,217";a="846571380" X-Received: from orsmsx601.amr.corp.intel.com ([10.22.229.14]) by fmsmga004.fm.intel.com with ESMTP/TLS/AES256-GCM-SHA384; 19 Dec 2023 19:46:03 -0800 X-Received: from orsmsx612.amr.corp.intel.com (10.22.229.25) by ORSMSX601.amr.corp.intel.com (10.22.229.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Tue, 19 Dec 2023 19:46:02 -0800 X-Received: from orsedg603.ED.cps.intel.com (10.7.248.4) by orsmsx612.amr.corp.intel.com (10.22.229.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35 via Frontend Transport; Tue, 19 Dec 2023 19:46:02 -0800 X-Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.101) by edgegateway.intel.com (134.134.137.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 19 Dec 2023 19:46:01 -0800 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J2hOV1zgJDr5rVYST2P9ixi92N0L0oKMS0k4i8ZCHmpzw7ps5yMLiAv6dGHCpn3Dgwdd3Qam3Ec+fNqgO4snAGcWtBWyxJCjGEbaCso4zM2Tzb/xYw3Yda8yHyD/xbClzOqJ5qpdH44P2GkLD5uGAcCatpr4BgJGr7LATc7tNqNfLkOBCUzNQsPPnWSbztDGMJYf77f01RfJxyj1e7ZvCm+Q290WOqK+fAXdTm/CWJa4N5ZDEHC6qwOJN4J+ZJxRe6poQ2AWSj6Nagf+9z7BlmwreYJ+kLFzfJXR3fslV+u+Q+jUFwL185iHG/DD61w1F6dQyNg3J0710Kp0abjOPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Qe2aguHqRSkQltbavbTgYm4iCF7aGz4AR5+4cAcz8iE=; b=dGehVDUwqjN5XwhfR/JozuQnexHptu5/8JyXzrBTfAivC+Yq8E11ZM/1vf5xgD8jJfeXoSTv3exQbXoLNXG+x8AGYA9+OVdrJVUnyTTDpstM+WRPgVmNw2PaLsfNLnJ6/a0S2vsBcOMN5AR5VVk4K9Q4JCrqXbvUSEuexDcYBSt2rRYPNzWxM94GReop6Q69drleSUEpl3JKCx33V+CcBqm6ei+vuCY5gaguHyNe+JPAdlPZtkreAYRtR+cm9yeoJI1sf9RSDDC1WUBAGAKi9OgJiqdhSUz9wo7BOfatT19JUx+JmUH8siUfRbrJghY8Ukun6Tczi4waOm8F6K8nrw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none X-Received: from BY5PR11MB3861.namprd11.prod.outlook.com (2603:10b6:a03:18d::13) by PH8PR11MB6561.namprd11.prod.outlook.com (2603:10b6:510:1c0::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7091.38; Wed, 20 Dec 2023 03:45:58 +0000 X-Received: from BY5PR11MB3861.namprd11.prod.outlook.com ([fe80::8243:8f57:5a76:c19b]) by BY5PR11MB3861.namprd11.prod.outlook.com ([fe80::8243:8f57:5a76:c19b%4]) with mapi id 15.20.7091.034; Wed, 20 Dec 2023 03:45:57 +0000 From: "Saloni Kasbekar" To: Sivaraman Nainar , "devel@edk2.groups.io" , "Clark-williams, Zachary" CC: Natalya Kalistratova , Dhanaraj V , Santhosh Kumar V , =?iso-2022-jp?B?R2VuZ1lvdSBaaG91ICgbJEI8fjkuTSQbKEIp?= Subject: Re: [edk2-devel] Clarification on LoadFile2 Protocol Installation for Network Boot Devices Thread-Topic: [EXTERNAL] RE: Clarification on LoadFile2 Protocol Installation for Network Boot Devices Thread-Index: AQHaL0nwlX1TCNDXtUGv2lauB4QO4LCve2SggAC2CTCAAOYt4A== Date: Wed, 20 Dec 2023 03:45:57 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-traffictypediagnostic: BY5PR11MB3861:EE_|PH8PR11MB6561:EE_ x-ms-office365-filtering-correlation-id: ba3df505-fb2e-4276-2994-08dc010e2d31 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam-message-info: p/TuikZSiTDuio20UWUSyxWseI8wiTKOpg5EHPHIvCc//TVfN92Y8IwuZ/x482igsFpdS06M6ijNUQ11zsm/cUL8UcVAtuP3q8FHEZ/BzuolLpqk6GbUl9uH3LNogu3Io0h9fzgX9id9GApT2s0R7v4rv4q39XTpx84J4oto1+hoFfdgqJQa31KvsBExt16PwYcsDj9xFn3HprcUBpkQxlUK4EMRz9s23Cgm8S26qQ61nEXEZqxzimu6xKsk+aQf0lawGkb4N9pvtEFbTgi/vqpRZmEDt3lVv98OlVanYpwGVNNoocLV1GrUXSUN9P/r9R8n+dQ1Qi7z5DLvno+iu30nlcKW8Tjd8wmUra+wa6d7+M4QUfIWCwvBbm1ryWCxKSMNIqYEI4AGlRSK9OulMSSgqEH9m6krXUU29XlBBtOhul+T6la4svNMkc2swFKgppidugEQVkXAp63dbNV/1YF5BT7xAWdzDpPHrQTnw7NbaHwGglumsAte7m9Yn75i75VoNsMgwh7fZ7kLzjXCp/4m91J1JM7mt9MIt9tA43aDXWQcE/hODNmV9cnJZ8A9heliv1XjcXlPJ9qwUc/KwcHYIr//ddb4zqrLHiJD2TDL5+T/7dxV6KoT8TITFZEkFpRmeBtifX5sHVLN7RP0hzP001V5fwDqgbGM9/SJ9xgeqY8n6wqJzL/17KMlmanXhqmDsa+lyN+ZeBQg9iWYYw== x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?iso-2022-jp?B?UEY1aERBYS9aZzhMV3IvUjdKenc1RDczemxMOU9Ud3Nyc3JLL3M4ZGVN?= =?iso-2022-jp?B?b1NxK3ZoOHgrZEI4Z3hFc2ZxOFFuWDBIbnRPTG41clpURXlIMmxLZnNM?= =?iso-2022-jp?B?NXR4RU5TWVl0VlNRMEFhY0g4WE9qYWdmRERveUlQd3NHK0NydDkwUFg1?= =?iso-2022-jp?B?NzYwRGh5eGJ0QmY3c1dsd3ZWNVN6SktEZ0pzMGZ1eEV4dDh5bzkzMHhy?= =?iso-2022-jp?B?STJDMk51c3FGZjZhYkxJNnBwU1E1dWU3Q3lqUWRyTHViU2pid09uVVpY?= =?iso-2022-jp?B?LzNMK0ZhN0VuY2IzaUszZWxSb3BLaTVQS3NxVG1EZWRoMlhrL3VIRGhs?= =?iso-2022-jp?B?amVFU1ozT3Rrby9RMDh3aXNzcGtPWktadC9pWTJSak1BWnRWbHdiMG4y?= =?iso-2022-jp?B?WDU3dElpR0pOOWRzODVnOURDREh3d3JWWUxUV25SK3V2RHVad2w0VTds?= =?iso-2022-jp?B?YktDeXBGUWxIK1RoRXFaTFNJRWRPRHNsd2d3cmRYNUpyN205K0tlK2R1?= =?iso-2022-jp?B?ODNlKzhyaU96aVB4SXJvVXpzQ3laTndpbXhVSmthci9uSkkzQUp0VGU5?= =?iso-2022-jp?B?cGFRUUZBOGplNlJTOU9QWFpHRVVKS25oN1ZzMEs5N1ZFemFicFdmMlFz?= =?iso-2022-jp?B?SlVpWXYvTFpWTVBOKzhiaHlac2tpbWJYTTE0dU1iQ2Y5MlYyVk9UWWlo?= =?iso-2022-jp?B?VnRzdkJQeWpDMVNibm4xNGNMUzdpWEV4WHlicjZEa2ticW1lRmJiSC9C?= =?iso-2022-jp?B?Y0RFRHFoMUVUb2xZREtBdzVqUzNqYVB0RFptNnJySnIzUlptMDZsdjFa?= =?iso-2022-jp?B?YmJON3ZWQmxNNjVrOGtzTzk5TUo5NDM2dkVldGk5M001MXY0SzI3SnNU?= =?iso-2022-jp?B?a2I2SC9tZ2RNUkNMVXNpdEtyM1VjYkhWZTFXYnA0a1pTajJmU3BqMEgx?= =?iso-2022-jp?B?a0NCd29MZVlPVlBhRHFzWmZhUG9NaGNXOW9rZDZ6WEJRelFxbUpOd0Rn?= =?iso-2022-jp?B?NG12ZFNad3JHVEUzODV2QytHRE0yZzJTM0VzeGU0SldMeTFQSUR5VDM0?= =?iso-2022-jp?B?WFI4U25wUkxMSjc3WHAxQWhOY2FzWnVGWnF1VVE4V2NtQnFaZHkrcUk5?= =?iso-2022-jp?B?RndvSkJHeHJtM3Z0akxOeVZ2OHR4QXN2QUxDQzE1NDc0dlE2Z2NRMEdH?= =?iso-2022-jp?B?dDdvN1g0eVAvMDV1b0pjeHdCVmxLWEpXL2hzcTJxRWsvMlYzaElkRGhY?= =?iso-2022-jp?B?TzhlbDhkcG1Zc1cwd3B4ZVlQbFVISmIzUVdaalUzdnMveUNXYkxXYXJE?= =?iso-2022-jp?B?RG1wV0JlRmZLR1N4WVB0SjFCSDgzOXFscG5rZkE0U0tNK0tTdjkvMjVX?= =?iso-2022-jp?B?NE5oZHduM0dlZVd6VGlnZ0lHc3gwU0NsdjZRVlhseGNVbStjWVJ4azZz?= =?iso-2022-jp?B?cTNheGlTdDAySDE1cm1DT2FuN1NRZ3o5MG9iUXBhcFNLTXRCYkRjbzM3?= =?iso-2022-jp?B?TWRTaEs4L3ZWcEYreVdkbTJma29Md01SREZPNk52U1cxMEVtZTFYWVRU?= =?iso-2022-jp?B?UTJyYmwrR01EUHQ2WlJmWXAwd0lTUENVYWV6c3JtY0sxd1hyM1IrS0hx?= =?iso-2022-jp?B?Q0hNblQ4c2R0VXBhcitkRFFidVV0dDVkbXNTc0VqSkk3UXNQNnMvVzlt?= =?iso-2022-jp?B?MUVNWFE1RG4xVWJ4cFY4b21CUDY4MU1sVFhrTW5Pdkt3TGprMHNZWkd6?= =?iso-2022-jp?B?RktLTVhCazEzcVQ0YUhDK3BYcUtkYUF2S0Q5b2pKaXRBT2FFSzRjbGQ2?= =?iso-2022-jp?B?SHRaclVTZTBVYmZUSVpjOWRFZ2x2UlBSM09qMk85U1JKZHgxUTEvTlFs?= =?iso-2022-jp?B?L1RNajIzMWpSUjEyckxRaDBDNkJOemRpSC9aMTVqYnZXbitqdk51bWR6?= =?iso-2022-jp?B?YjRxM1BvTDdxZllrMzFKOGNJWXdVbzgyNDVidXZHUUpWbTVCcHJGZGVF?= =?iso-2022-jp?B?QVdMRzc1bldMemtXTmhaZDNCd1FkMnVFeUkyWXpxbTN5ck5pVVNYSmlY?= =?iso-2022-jp?B?TGo1UTVmcDJGSUZza01sdmpKRVZJcFF6aFN2WHA1NzdWK0pQS3JYNDEy?= =?iso-2022-jp?B?a2N3aDk1VlZvY2g1Y3JudEVGblZKMkkzT3ErVmZ5Yk10QTRiWXBaUEI2?= =?iso-2022-jp?B?aVYwL1VsOXBESk1HVDlGTW9lNkpuN24xMnNsdHYyL2t2Q3Vpc0RWV1FF?= =?iso-2022-jp?B?TWpyNnZrYXVsVEZtTXlSUkRzRlNNaVpjZGJsb1U0UGJxam1tcVFKNFFX?= =?iso-2022-jp?B?WTlDYQ==?= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB3861.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: ba3df505-fb2e-4276-2994-08dc010e2d31 X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Dec 2023 03:45:57.8684 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: rKRqrXJAyAcKiOB6ErEEnNqW2diJeDJa+gPuZcBU+fy8l66i/v2V+FPysrh4mdy/2X8oldtRqc+OpS4hE7Ne9LidxWv2CFTmoqiqmmeCCl4= X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH8PR11MB6561 X-OriginatorOrg: intel.com Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,saloni.kasbekar@intel.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: KH3CBC68IDqRS0C0qhrB74rWx7686176AA= Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BY5PR11MB386167E087CBF9DA84D814C0F196ABY5PR11MB3861namp_" X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=TCBMcx6F; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=intel.com (policy=none); arc=reject ("signature check failed: fail, {[1] = sig:microsoft.com:reject}") --_000_BY5PR11MB386167E087CBF9DA84D814C0F196ABY5PR11MB3861namp_ Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable Hi Siva, We can file a Mantis for the UEFI forum with the proposal to update the wor= ding for #18 to include Network devices. Thanks, Saloni From: Sivaraman Nainar Sent: Monday, December 18, 2023 10:54 PM To: Kasbekar, Saloni ; devel@edk2.groups.io; Cla= rk-williams, Zachary Cc: Natalya Kalistratova ; Dhanaraj V = ; Santhosh Kumar V ; GengYou Zhou (=1B$B<~9.M$=1B(B= ) Subject: RE: [EXTERNAL] RE: Clarification on LoadFile2 Protocol Installatio= n for Network Boot Devices Hello Saloni: Thanks for Clarifying. Yes. If Network Devices MUST install LoadFile2 then it would be good that s= ection 18 includes network devices. Do we need to request UEFI forum for th= e same? Thanks Siva From: Kasbekar, Saloni > Sent: Tuesday, December 19, 2023 1:41 AM To: devel@edk2.groups.io; Sivaraman Nainar >; Clark-williams, Zachary > Cc: Natalya Kalistratova >; Dhana= raj V >; Santhosh Kumar V >; GengYou Zhou (=1B$B<~9.= M$=1B(B) > Subject: [EXTERNAL] RE: Clarification on LoadFile2 Protocol Installation fo= r Network Boot Devices **CAUTION: The e-mail below is from an external source. Please exercise cau= tion before opening attachments, clicking links, or following guidance.** Hi Siva, =1B$B!H=1B(BThe EFI_LOAD_FILE2_PROTOCOL is a simple protocol used to obtain= files from arbitrary devices that are not boot options=1B$B!I=1B(B =1B$B!H=1B(BThe EFI_LOAD_FILE_PROTOCOL is used for devices that do not dire= ctly support file systems. Network devices commonly boot in this model where the image is materialized without the nee= d of a file system.=1B$B!I=1B(B Based on the above statements, I believe the Network stack is fine using th= e current EFI_LOAD_FILE_PROTOCOL and not the EFI_LOAD_FILE2_PROTOCOL as the= y are currently loaded as boot options. We currently do install the EFI_LOA= D_FILE_PROTOCOL within the Network stack. Eg - // // Create a child handle for the HTTP boot and install DevPath and Load f= ile protocol on it. // CopyMem (&Private->Ip6Nic->LoadFile, &gHttpBootDxeLoadFile, sizeof (Priva= te->LoadFile)); Status =3D gBS->InstallMultipleProtocolInterfaces ( &Private->Ip6Nic->Controller, &gEfiLoadFileProtocolGuid, &Private->Ip6Nic->LoadFile, &gEfiDevicePathProtocolGuid, Private->Ip6Nic->DevicePath, NULL ); Maybe we need to update #18 to include Network devices? Thanks, Saloni From: devel@edk2.groups.io > On Behalf Of Sivaraman Nainar via groups.i= o Sent: Friday, December 15, 2023 3:29 AM To: devel@edk2.groups.io; Clark-williams, Zach= ary >; Kasbekar, Saloni > Cc: Natalya Kalistratova >; Dhana= raj V >; Santhosh Kumar V >; GengYou Zhou (=1B$B<~9.= M$=1B(B) > Subject: [edk2-devel] reg: Clarification on LoadFile2 Protocol Installation= for Network Boot Devices Hello ZClarkWilliams: Could you please help to clarify if NetworkStack MUST install the LoadFile2= Protocol or not. With reference to the below spec item, the LoadFile2 prot= ocol must be implemented. In one of the BIOS environment, the Setup Browser Locates the LoadFile2 ins= tance of Network Boot Device and it not found as it not installed by the cu= rrent NetworkPkg. Can you please comment if there is any reason behind not installing during = the HTTP Boot. =1B$B!H=1B(BUEFI SPEC 2.6.3 Driver-Specific Elements There are a number of UEFI elements that can= be added or removed depending on the features that a specific driver requi= res. Drivers can be implemented by platform firmware developers to support = buses and devices in a specific platform. Drivers can also be implemented b= y add-in card vendors for devices that might be integrated into the platfor= m hardware or added to a platform through an expansion slot. The following = list includes possible driver features, and the UEFI elements that are requ= ired for each feature type: 1. If a driver is written for a boot device that is not a block-oriented= device, a file system-based device, or a console device, then the EFI_LOAD= _FILE2_PROTOCOL must be implemented. =1B$B!H=1B(B Thanks Siva -The information contained in this message may be confidential and propriet= ary to American Megatrends (AMI). This communication is intended to be read= only by the individual or entity to whom it is addressed or by their desig= nee. If the reader of this message is not the intended recipient, you are o= n notice that any distribution of this message, in any form, is strictly pr= ohibited. Please promptly notify the sender by reply e-mail or by telephone= at 770-246-8600, and then delete or destroy all copies of the transmission= . -The information contained in this message may be confidential and propriet= ary to American Megatrends (AMI). This communication is intended to be read= only by the individual or entity to whom it is addressed or by their desig= nee. If the reader of this message is not the intended recipient, you are o= n notice that any distribution of this message, in any form, is strictly pr= ohibited. Please promptly notify the sender by reply e-mail or by telephone= at 770-246-8600, and then delete or destroy all copies of the transmission= . -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#112741): https://edk2.groups.io/g/devel/message/112741 Mute This Topic: https://groups.io/mt/103249982/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- --_000_BY5PR11MB386167E087CBF9DA84D814C0F196ABY5PR11MB3861namp_ Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable

Hi Siva,

 

We can file a Mantis for the UEFI forum w= ith the proposal to update the wording for #18 to include Network devices.<= o:p>

 

Thanks,

Saloni

 

From: Sivaraman Nainar <sivaramann@ami.com>
Sent: Monday, December 18, 2023 10:54 PM
To: Kasbekar, Saloni <saloni.kasbekar@intel.com>; devel@edk2.g= roups.io; Clark-williams, Zachary <zachary.clark-williams@intel.com><= br> Cc: Natalya Kalistratova <NatalyaK@ami.com>; Dhanaraj V <vd= hanaraj@ami.com>; Santhosh Kumar V <santhoshkumarv@ami.com>; GengY= ou Zhou (=1B$B<~9.M$=1B(B) <GengYouZhou@ami.com>
Subject: RE: [EXTERNAL] RE: Clarification on LoadFile2 Protocol Inst= allation for Network Boot Devices

 

Hello Sal= oni:

 

Thanks fo= r Clarifying.

 

Yes. If N= etwork Devices MUST install LoadFile2 then it would be good that section 18= includes network devices. Do we need to request UEFI forum for the same?

 

Thanks

Siva

From: Kasbekar, Saloni <saloni.kasbekar@intel.com>
Sent: Tuesday, December 19, 2023 1:41 AM
To: devel@edk2.groups.io= ; Sivaraman Nainar <sivaramann@ami= .com>; Clark-williams, Zachary <zachary.clark-williams@intel.com>
Cc: Natalya Kalistratova <Nat= alyaK@ami.com>; Dhanaraj V <= vdhanaraj@ami.com>; Santhosh Kumar V <santhoshkumarv@ami.com>; GengYou Zhou (=1B$B<~9.M$=1B(B) <Ge= ngYouZhou@ami.com>
Subject: [EXTERNAL] RE: Clarification on LoadFile2 Protocol Installa= tion for Network Boot Devices

 

 

**CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links= , or following guidance.**

Hi Siva,

 

=1B$B!H=1B(BThe EFI_LOAD_FILE2_PROTOCO= L is a simple protocol used to obtain files from arbitrary devices that are= not boot

options=1B$B!I=1B(B

=1B$B!H=1B(BThe EFI_LOAD_FILE_PROTOCOL= is used for devices that do not directly support file systems. Network dev= ices

commonly boot in this model where the = image is materialized without the need of a file system.=1B$B!I=1B(B=

 

Based on the above statements, I believe = the Network stack is fine using the current EFI_LOAD_FILE_PROTOCOL and not = the EFI_LOAD_FILE2_PROTOCOL as they are currently loaded as boot options. We currently do install the EFI_LOAD_FILE_PROTOCOL= within the Network stack. Eg –

  //

  // Create a child handle for the H= TTP boot and install DevPath and Load file protocol on it.

  //

  CopyMem (&Private->Ip6Nic-&= gt;LoadFile, &gHttpBootDxeLoadFile, sizeof (Private->LoadFile));

  Status =3D gBS->InstallMultiple= ProtocolInterfaces (

       = ;           &Private-= >Ip6Nic->Controller,

       = ;           &gEfiLoad= FileProtocolGuid,

       = ;           &Private-= >Ip6Nic->LoadFile,

       = ;           &gEfiDevi= cePathProtocolGuid,

       = ;           Private->I= p6Nic->DevicePath,

       = ;           NULL

       = ;           );

 

Maybe we need to update #18 to include Ne= twork devices?

 

Thanks,

Saloni

 

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Sivaraman Nainar via groups.io
Sent: Friday, December 15, 2023 3:29 AM
To: devel@edk2.groups.io= ; Clark-williams, Zachary <zachary.clark-williams@intel.com>; Kasbekar, Saloni <saloni.kasbekar@intel.com> Cc: Natalya Kalistratova <Nat= alyaK@ami.com>; Dhanaraj V <= vdhanaraj@ami.com>; Santhosh Kumar V <santhoshkumarv@ami.com>; GengYou Zhou (=1B$B<~9.M$=1B(B) <GengYouZhou@ami.com>
Subject: [edk2-devel] reg: Clarification on LoadFile2 Protocol Insta= llation for Network Boot Devices

 

Hello ZClarkWilliams:

 

Could you please help to clarify if NetworkStack MUS= T install the LoadFile2 Protocol or not. With reference to the below spec i= tem, the LoadFile2 protocol must be implemented.

 

In one of the BIOS environment, the Setup Browser Lo= cates the LoadFile2 instance of Network Boot Device and it not found as it = not installed by the current NetworkPkg.

 

Can you please comment if there is any reason behind= not installing during the HTTP Boot.

=1B$B!H=1B(= BUEFI SPEC

2.6.3 Driver-S= pecific Elements There are a number of UEFI elements that can be added or r= emoved depending on the features that a specific driver requires. Drivers can be implemented by platform firmwar= e developers to support buses and devices in a specific platform. Drivers c= an also be implemented by add-in card vendors for devices that might be int= egrated into the platform hardware or added to a platform through an expansion slot. The following list inclu= des possible driver features, and the UEFI elements that are required for e= ach feature type:

  1. If a driver is written = for a boot device that is not a block-oriented device, a file system-based = device, or a console device, then the EFI_LOAD_FILE2_PROTOCOL must be imple= mented.

=1B$B!H=1B(B

 

Thanks

Siva

-The information contained in= this message may be confidential and proprietary to American Megatrends (A= MI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their desig= nee. If the reader of this message is not the intended recipient, you are o= n notice that any distribution of this message, in any form, is strictly pr= ohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delet= e or destroy all copies of the transmission.

-The info= rmation contained in this message may be confidential and proprietary to Am= erican Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is address= ed or by their designee. If the reader of this message is not the intended = recipient, you are on notice that any distribution of this message, in any = form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600= , and then delete or destroy all copies of the transmission.

_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#112741) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
--_000_BY5PR11MB386167E087CBF9DA84D814C0F196ABY5PR11MB3861namp_--