public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Karunakar P <karunakarp@amiindia.co.in>
To: "'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Subject: Re: Failed to clear configuration in Ip4Config2 Protocol
Date: Fri, 15 Sep 2017 09:40:39 +0000	[thread overview]
Message-ID: <A885E3F3F1F22B44AF7CC779C062228EE0669AB3@VENUS1.in.megatrends.com> (raw)
In-Reply-To: <A885E3F3F1F22B44AF7CC779C062228EE06697B5@VENUS1.in.megatrends.com>

Hello All,

Could you please anyone provide comment on this?

Thank you,
karunakar

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

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 is 0 and Data is NULL

    Status = Ip4Cfg2->SetData (

                        Ip4Cfg2,

                        Ip4Config2DataTypeManualAddress,

                        0,

                        0

                        );

3.       But SetData returns with Write Protected Error Status        // Status = Write Protected

4.        Faced the same error for setting Gateway & DnsServer

Guess the return is happening from
Ip4Config2SetManualAddress() ->
...
  if (Instance->Policy != Ip4Config2PolicyStatic) {
    return EFI_WRITE_PROTECTED;
  }
...

Could you please help on this whether am I missing anything or anything else need to be done to resolve this?

Thanks,
karunakar


From: Karunakar P
Sent: Wednesday, September 13, 2017 7:00 PM
To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
Subject: RE: Failed to clear configuration in Ip4Config2 Protocol

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 is 0 and Data is NULL

    Status = Ip4Cfg2->SetData (

                        Ip4Cfg2,

                        Ip4Config2DataTypeManualAddress,

                        0,

                        0

                        );

3.       But SetData returns with Write Protected Error Status        // Status = Write Protected

4.        Faced the same error for setting Gateway &DnsServer

Guess the error is happening from


Thanks,
karunakar


  reply	other threads:[~2017-09-15  9:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 13:29 Failed to clear configuration in Ip4Config2 Protocol Karunakar P
2017-09-13 13:33 ` Karunakar P
2017-09-15  9:40   ` Karunakar P [this message]
2017-09-18  2:16     ` Wu, Jiaxin
2017-09-18  4:22       ` Karunakar P
2017-09-18  4:57         ` Wu, Jiaxin
2017-09-19 10:52           ` Karunakar P
2017-09-20  2:11             ` Wu, Jiaxin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A885E3F3F1F22B44AF7CC779C062228EE0669AB3@VENUS1.in.megatrends.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox