From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 1532A21E945E2 for ; Sun, 17 Sep 2017 21:19:27 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 99FFB82055; Mon, 18 Sep 2017 09:55:09 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8D67E8204A; Mon, 18 Sep 2017 09:55:09 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Mon, 18 Sep 2017 09:55:09 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Mon, 18 Sep 2017 09:52:26 +0530 From: Karunakar P To: "'Wu, Jiaxin'" , "'edk2-devel@lists.01.org'" , "Ye, Ting" Thread-Topic: [edk2] Failed to clear configuration in Ip4Config2 Protocol Thread-Index: AQHTMCQmiCYvM1TUUU+NimAGukLtxKK6Bcvw Date: Mon, 18 Sep 2017 04:22:25 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B727416332C12@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B727416332C12@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.128] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23336.004 X-TM-AS-Result: No--10.323-5.0-31-10 X-imss-scan-details: No--10.323-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23336.004 X-TMASE-Result: 10--10.323300-10.000000 X-TMASE-MatchedRID: 8+bhjh9TQnF5X0FJZbmEppmug812qIbzWDdWpJMntKhXmMLGp+plrWp5 n4DMEybN4FD3otNxTUPiN7d6wVysWYov7n0dV+r8FYJUGv4DL3wppGYMKZezN45t/XRqktxJp7u eaEkDqTNe9N8X0ShXYNlpdJfSf9QlbjrdvKT0VGK0sO72q2op4dJ178I1tpklEmV87nTVGCBaQx qSb3eFWMcf83XSWDzmrc7IpCMhA0aOUvUSGKdRPjo39wOA02LhIWrhso05H/Vh7WbOnt2TB/5QP McorVJCgHpD5xuuxKj1VmTZnVKT+HdWNVeH9NKP+L2GsArAgtqSTnFzEHOIwRHfiujuTbedOlt9 1MBw1ebi8zVgXoAltr9FcG1YeQieVnRXm1iHN1bEQdG7H66TyH4gKq42LRYkF9/G2xB2S5QBZvH tZuBrWGnM7WbgUEYlAKg9z4S77Vd+3BndfXUhXQ== X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 Subject: Re: Failed to clear configuration in Ip4Config2 Protocol 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: Mon, 18 Sep 2017 04:19:27 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Jiaxin, Thank you very much for your info, Yes it works fine for manual configurati= on. And also could you please provide steps to verify "Add DNS device path node= " feature.=20 Thanks, karunakar -----Original Message----- From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com]=20 Sent: Monday, September 18, 2017 7:46 AM To: Karunakar P; 'edk2-devel@lists.01.org'; Ye, Ting Subject: RE: [edk2] Failed to clear configuration in Ip4Config2 Protocol Hi Karunakar, According the UEFI Spec, the Ip4Config2DataTypeManualAddress, Ip4Config2Dat= aTypeGateway and Ip4Config2DataTypeDnsServer configuration data are not all= owed to set via SetData() if the policy is DHCP. So, the clear feature is o= nly for the manual configuration. This is our design purpose and also the = reason why the feature is not apply to the Ip4Config2DataTypeInterfaceInfo/= Ip4Config2DataTypePolicy. Thanks, Jiaxin > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of=20 > Karunakar P > Sent: Friday, September 15, 2017 5:41 PM > To: 'edk2-devel@lists.01.org' > Subject: Re: [edk2] Failed to clear configuration in Ip4Config2=20 > Protocol >=20 > Hello All, >=20 > Could you please anyone provide comment on this? >=20 > Thank you, > karunakar >=20 > From: Karunakar P > Sent: Wednesday, September 13, 2017 7:04 PM > To: 'edk2-devel@lists.01.org' > Subject: RE: RE: Failed to clear configuration in Ip4Config2 Protocol >=20 > Hello All, >=20 > I was trying to verify the feature "Allow SetData to clear=20 > configuration in Ip4Config2/Ip6Config Protocol" , But SetData returns=20 > with Write Protected Error Status >=20 > [Steps followed] >=20 > 1. I've taken the above feature changes. >=20 > 2. I've a UEFI test Application which call to SetData with DataSize= is 0 and > Data is NULL >=20 > Status =3D Ip4Cfg2->SetData ( >=20 > Ip4Cfg2, >=20 > Ip4Config2DataTypeManualAddress, >=20 > 0, >=20 > 0 >=20 > ); >=20 > 3. But SetData returns with Write Protected Error Status // = Status =3D > Write Protected >=20 > 4. Faced the same error for setting Gateway & DnsServer >=20 > Guess the return is happening from > Ip4Config2SetManualAddress() -> > ... > if (Instance->Policy !=3D Ip4Config2PolicyStatic) { > return EFI_WRITE_PROTECTED; > } > ... >=20 > Could you please help on this whether am I missing anything or=20 > anything else need to be done to resolve this? >=20 > Thanks, > karunakar >=20 >=20 > From: Karunakar P > Sent: Wednesday, September 13, 2017 7:00 PM > To: edk2-devel@lists.01.org > Subject: RE: Failed to clear configuration in Ip4Config2 Protocol >=20 > Hello All, >=20 > I was trying to verify the feature "Allow SetData to clear=20 > configuration in Ip4Config2/Ip6Config Protocol" , But SetData returns=20 > with Write Protected Error Status >=20 > [Steps followed] >=20 > 1. I've taken the above feature changes. >=20 > 2. I've a UEFI test Application which call to SetData with DataSize= is 0 and > Data is NULL >=20 > Status =3D Ip4Cfg2->SetData ( >=20 > Ip4Cfg2, >=20 > Ip4Config2DataTypeManualAddress, >=20 > 0, >=20 > 0 >=20 > ); >=20 > 3. But SetData returns with Write Protected Error Status // = Status =3D > Write Protected >=20 > 4. Faced the same error for setting Gateway &DnsServer >=20 > Guess the error is happening from >=20 >=20 > Thanks, > karunakar > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel