public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sivaraman Nainar" <sivaramann@amiindia.co.in>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "jiaxin.wu@intel.com" <jiaxin.wu@intel.com>,
	"Rabeda, Maciej" <maciej.rabeda@linux.intel.com>
Subject: reg: Wifi Connection Manager Setup Page Issues
Date: Fri, 8 May 2020 03:04:21 +0000	[thread overview]
Message-ID: <B4DE137BDB63634BAC03BD9DE765F19702AF1C6EBB@Venus2.in.megatrends.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

Hello,
Getting an issue in Wifi Connection Manager Setup page when UEFI Spec 2.8 BrowserCallback specific changes integrated in Setup Browser.
According to UEFI Spec 2.8, Browser Callback is allowed to call only from Driver's ConfigAccess protocol and via ConfigAccess->Callback() it allowed for all type of actions except EFI_BROWSER_ACTION_FORM_OPEN.
WifiMgrDxeHiiConfigAccessCallback() is the callback function of WifiConnectionMgr. In this callback Security Type IfrData is updated on action EFI_BROWSER_ACTION_FORM_OPEN.  When the setup browser is not invoking the WifiMgrDxeHiiConfigAccessCallback in EFI_BROWSER_ACTION_FORM_OPEN action the control value not updated hence the browser does not show the Security Password control. The VFR suppress the Password control and shows the control only when SecurityType is SECURITY_TYPE_WPA2_PERSONAL.
Would you please feedback how this can be addressed?
-Siva

[-- Attachment #2: Type: text/html, Size: 3316 bytes --]

             reply	other threads:[~2020-05-08  3:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  3:04 Sivaraman Nainar [this message]
     [not found] <160CEEA2C84817A9.8752@groups.io>
2020-05-15 11:54 ` reg: Wifi Connection Manager Setup Page Issues Sivaraman Nainar
2020-05-19  9:11   ` Dandan Bi
2020-08-18  9:52     ` Sivaraman Nainar

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=B4DE137BDB63634BAC03BD9DE765F19702AF1C6EBB@Venus2.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