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 21FDE20945BE6 for ; Wed, 13 Sep 2017 06:26:52 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 22DE382047 for ; Wed, 13 Sep 2017 19:02:27 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0CA3782046 for ; Wed, 13 Sep 2017 19:02:27 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Wed, 13 Sep 2017 19:02:27 +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; Wed, 13 Sep 2017 18:59:46 +0530 From: Karunakar P To: "edk2-devel@lists.01.org" Thread-Topic: RE: Failed to clear configuration in Ip4Config2 Protocol Thread-Index: AdMskj7BWl5bVzVoSqGYPpbI86DnSA== Date: Wed, 13 Sep 2017 13:29:45 +0000 Message-ID: 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-23326.007 X-TM-AS-Result: No--13.928-5.0-31-10 X-imss-scan-details: No--13.928-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23326.007 X-TMASE-Result: 10--13.928000-10.000000 X-TMASE-MatchedRID: oHOSwQSJZWgRWAL+HrpOq4QnnAFRgjn9Xs5nqGvDCfOrzPs85fwUkwe0 jlRIZ0jueDnJ+6MMQbwhAHXhxeDwKl/nxjqa1wO9RlqShqb35p5A8JZETQujwk1KG1YrOQW/f/b TCoZRptI22uoEm245fkFWCvm86w840sXpjQvtH9Abrq24GKfh0Oq/uWzz2rh3+TdKNkxxkWSoBV 9sc+TYx+I+Ja+Fp+EYrBBSnn/GVMan+dP7GcjVHbqQyAveNtg6Mx981lgKTcP7n73d09vr9zdb7 25U3Cx8S+eT5OICrfYiiDah36Jf597M71Z6QWc4SDkh6bW+bccvcKmqjEcY3uO53bHtM9W3Fj/F nq7VF8xSEHEvdGPYmvcml4T4Z1GdgiIO7Sf/7rGL6bUMM+bbIjPYPmH3aiShVNFVtrDWmzo4BNe SqPakoTjWB0c64C3n1UjFGrktczaXBXaJoB9JZxRFJJyf5BJeyJ1gFgOMhOmJoeB6BijRISq2rl 3dzGQ1xviq56ZjooA17JXdmwb+LTZsej7ICsfKQ+W3Fl8wdzbQhUz6WWUFAU4iwi6Nn2YJv5ppJ iMdhU/2yw2AFNMflbO1ZYPK8qMEaMZp8XFlHp9+3BndfXUhXQ== X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 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: Wed, 13 Sep 2017 13:26:52 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, I was trying to verify the feature "Allow SetData to clear configuration in= Ip4Config2/Ip6Config Protocol" , But SetData returns with Write Protected = Error Status [Steps followed] 1. I've taken the above feature changes. 2. I've a UEFI test Application which call to SetData with DataSize i= s 0 and Data is NULL Status =3D Ip4Cfg2->SetData ( Ip4Cfg2, Ip4Config2DataTypeManualAddress, 0, 0 ); 3. But SetData returns with Write Protected Error Status // St= atus =3D Write Protected 4. Faced the same error for setting Gateway &DnsServer Guess the error is happening from Thanks, karunakar