From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [14.98.235.2]) by mx.groups.io with SMTP id smtpd.web10.11655.1589543741288393354 for ; Fri, 15 May 2020 04:55:42 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=SPF record not found (domain: amiindia.co.in, ip: 14.98.235.2, mailfrom: sivaramann@amiindia.co.in) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4F7A482047; Fri, 15 May 2020 17:34:00 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 24F4C82046; Fri, 15 May 2020 17:34:00 +0530 (IST) Received: from webmail.amiindia.co.in (venus1.in.megatrends.com [10.0.0.5]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Fri, 15 May 2020 17:34:00 +0530 (IST) Received: from VENUS2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b]) by VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5%14]) with mapi id 14.01.0438.000; Fri, 15 May 2020 17:25:56 +0530 From: "Sivaraman Nainar" To: "jiaxin.wu@intel.com" , "Rabeda, Maciej" , "dandan.bi@intel.com" CC: "devel@edk2.groups.io" , Sivaraman Nainar Subject: Re: reg: Wifi Connection Manager Setup Page Issues Thread-Topic: reg: Wifi Connection Manager Setup Page Issues Thread-Index: AdYk5UJpOlhlXrj0Tfq+Jy2vYp6FkwFyhOyA Date: Fri, 15 May 2020 11:54:48 +0000 Message-ID: References: <160CEEA2C84817A9.8752@groups.io> In-Reply-To: <160CEEA2C84817A9.8752@groups.io> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [106.198.86.209] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1817-8.5.0.1020-25420.007 X-TM-AS-Result: No--27.163-5.0-31-10 X-imss-scan-details: No--27.163-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1817-8.5.1020-25420.007 X-TMASE-Result: 10--27.162600-10.000000 X-TMASE-MatchedRID: vWvnoyq7eMw7iuZ/mdYYtgzvg1/q1MH2xjfJ+i+nbHQxicNUzIllO5Y7 CMQ0zfkMOsTWN15M+Os9oFMnLLzjBRmyTBaqiJvclRlSJ4kxbonw5sfLGppYYtlIpzh8STh1cyo ubH86anWI2r05I9xqU4w3R5nVipOzqNmmMLp35Z/5LkL/TyFZzU4dB39zev5YjjoTxaO+A594q1 YuaXXg/0Tfju1jt+vfOGJyJBH/4NBa0OEIdxUCnqJrsuGRVZst4Ukt7v4TdmaGsnlHOiGwocjdt jHY+jGWs1RWeqLGIw4wo+sXt0rnszH+T3YvtHy2P/mlMDR9HNS7+r627MDAzAdnH3FQrCBXRfz7 IWB2L9su+/ZxS0sr+1MV11xUs7fNZaWoKfR05a/MEmMJ+LiV/Q05t9LK+kfyfuQW+l720Km7fjw ZEcnD7OzhkZcJwPyQGgp0q+mz1yjfVqwz+CynaRgO7sCGTR0NXF/PXQ6xePlXoWfCQzKBl153Jz 3EoJGotAnihQXnq+hnq6caWcIOC3EONw67gSVceuOjdf174Md52B7qixELqCijDpqG0ehhUD0YH Qo4AcDvOC1QV7aBzhL2CF0ShhNIGfESeH6pl4Zvn11REP3xnm7CfwvjKCB+YfTOuJNXWLvXNo5M GjcKoN/xBY6jZqnZRR+qE4iJsId7NIjco1DV8jg2jfgv3Zp9UdfEKc10rU75B8XGyV5ZNygu5Gb K38XEoqoK5yz0eVIUBWY02fqT/Wjdirk8LAsCpDHbtE2qhVlbMIL4mcV7Cet0I3K+xA9R7RdE/6 60qlh4TfcMEN543juUqTPTfDTrfS0Ip2eEHnyvXSmSdlcYms8943oc3p3sCpjkNJegF9sq0hzNA 57lIr6HSs9zZy6jeSC65CityAx5WCB2GnFhw+irYypktXRWprz/tKLnZhI7VSCsloIkPn7cGd19 dSFd X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B4DE137BDB63634BAC03BD9DE765F19702AF1CF25FVenus2inmegat_" --_000_B4DE137BDB63634BAC03BD9DE765F19702AF1CF25FVenus2inmegat_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Jiaxin / Dandan: Could you please provide your comments. -Siva From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Siva= raman Nainar Sent: Friday, May 8, 2020 8:34 AM To: devel@edk2.groups.io Cc: jiaxin.wu@intel.com; Rabeda, Maciej Subject: [edk2-devel] reg: Wifi Connection Manager Setup Page Issues 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 WifiConnec= tionMgr. In this callback Security Type IfrData is updated on action EFI_BR= OWSER_ACTION_FORM_OPEN. When the setup browser is not invoking the WifiMgr= DxeHiiConfigAccessCallback in EFI_BROWSER_ACTION_FORM_OPEN action the contr= ol value not updated hence the browser does not show the Security Password = control. The VFR suppress the Password control and shows the control only w= hen SecurityType is SECURITY_TYPE_WPA2_PERSONAL. Would you please feedback how this can be addressed? -Siva This e-mail is intended for the use of the addressee only and may contain = privileged, confidential, or proprietary information that is exempt from di= sclosure under law. If you have received this message in error, please info= rm us promptly by reply e-mail, then delete the e-mail and destroy any prin= ted copy. Thank you. --_000_B4DE137BDB63634BAC03BD9DE765F19702AF1CF25FVenus2inmegat_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Jiaxin / Dandan= :

Could you please prov= ide your comments.

-Siva

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Beha= lf Of Sivaraman Nainar
Sent: Friday, May 8, 2020 8:34 AM
To: devel@edk2.groups.io
Cc: jiaxin.wu@intel.com; Rabeda, Maciej
Subject: [edk2-devel] reg: Wifi Connection Manager Setup Page Issue= s

 

Hello,

Getting an issue in Wifi Connection Manager Setup p= age when UEFI Spec 2.8 BrowserCallback specific changes integrated in Setup= Browser.

According to UEFI Spec 2.8, Browser Callback is all= owed 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 u= pdated 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 henc= e 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

This e-mail is intended for the use of the addressee only = and may contain privileged, confidential, or proprietary information that i= s exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then de= lete the e-mail and destroy any printed copy. Thank you.

--_000_B4DE137BDB63634BAC03BD9DE765F19702AF1CF25FVenus2inmegat_--