public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bi, Dandan" <dandan.bi@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Dong, Eric" <eric.dong@intel.com>, "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu
Date: Thu, 12 Apr 2018 06:07:33 +0000	[thread overview]
Message-ID: <3C0D5C461C9E904E8F62152F6274C0BB3BAA4ECF@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103BAAC347@shsmsx102.ccr.corp.intel.com>

Good suggestion. Thanks Star.
 I will cover them in V2 patches.

Thanks,
Dandan
-----Original Message-----
From: Zeng, Star 
Sent: Thursday, April 12, 2018 2:03 PM
To: Bi, Dandan <dandan.bi@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
Cc: Dong, Eric <eric.dong@intel.com>; Gao, Liming <liming.gao@intel.com>; Zeng, Star <star.zeng@intel.com>
Subject: RE: [edk2] [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu

If the cases can be listed completely, then it will be better to also add them in the comments for the two GUIDs, then consumer can easily know them.


Thanks,
Star
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Bi, Dandan
Sent: Thursday, April 12, 2018 11:47 AM
To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
Cc: Bi, Dandan <dandan.bi@intel.com>; Dong, Eric <eric.dong@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: Re: [edk2] [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu

Hi all,

All setup menu enter/exit cases includes:
a.	UiApp entry point is called and then setup menu is shown                (enter setup menu) 
b.	User select Continue menu in setup menu to exit.                                (exit setup menu)
c.	User select Reset menu in setup page to leave exit.                             (exit setup menu)
d.	User boot from file to exit setup page.                                                        (exit setup menu)
e.	Exit from boot from file and return to UiApp.                                           (enter setup menu)
f.	User boot from boot manager to exit setup page.                                  (exit setup menu)
g.            Exit the boot option in boot manager and return to UiApp.                (enter setup menu)

I didn't describe it in details in the commit messages.  I am sorry that if it make you confused.
I will add them in the commit messages of V2 patches.


Thanks,
Dandan

-----Original Message-----
From: Bi, Dandan
Sent: Thursday, April 12, 2018 11:17 AM
To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
Cc: Dong, Eric <eric.dong@intel.com>; Gao, Liming <liming.gao@intel.com>; Bi, Dandan <dandan.bi@intel.com>
Subject: RE: [edk2] [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu

Hi Mike,

We can't move the enter/exit event signaling into the FormBrowwer SendForm() function.

Because we can't decide whether enter/exit setup through SendForm() is called or not.  Some examples:

1. SendForm() is not called when exit setup menu and re-enter setup menu. Such as, SendForm() is only called when enter front page firstly. But when  go to Boot Manager menu to select an option to boot and exit setup menu, then exit the option and return to setup menu, SendForm() is not called in this case.

2. SendForm () may be also called more than one time even if we don't  leave setup menu. Such as, if we want to add an boot option in setup menu, when choose file to add boot option, SendForm() will be called to show files. But we don't  think we leave setup menu in this case.

So if we signal setup enter/exit event in SendForm(), may cause less/more notifications. Which is not a correct behavior.


Thanks,
Dandan

-----Original Message-----
From: Kinney, Michael D
Sent: Thursday, April 12, 2018 9:44 AM
To: Bi, Dandan <dandan.bi@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: Dong, Eric <eric.dong@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: RE: [edk2] [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu

Dandan Bi,

Is it possible to move the enter/exit event signaling into the FormBrowwer SendForm() function?  The current patch set adds these signal calls in all the places that
SendForm() is called and if one of these is missed, a notification will be missed.

Mike

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> bounces@lists.01.org] On Behalf Of Dandan Bi
> Sent: Wednesday, April 11, 2018 6:32 PM
> To: edk2-devel@lists.01.org
> Cc: Dong, Eric <eric.dong@intel.com>; Gao, Liming 
> <liming.gao@intel.com>
> Subject: [edk2] [patch 0/3] MdeModulePkg/UiApp: Signal event when 
> enter/exit setup menu
> 
> These changes are to support notify callbacks when enter/exit setup 
> menu, since some driver may need to hook setup enter/exit points to do 
> something.
> 
> We will signal setup enter/exit events for all setup menu enter/exit 
> cases.Then the module which pay attention to these events can execute 
> the callback.
> 
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Dandan Bi <dandan.bi@intel.com>
> 
> Dandan Bi (3):
>   MdeModulePkg/UiApp: Signal event when enter/exit setup menu
>   MdeModulePkg/BMMUiLib: Signal event when enter/exit setup menu
>   MdeModulePkg/BMUiLib: Signal event when enter/exit setup menu
> 
>  MdeModulePkg/Application/UiApp/FrontPage.c
> | 4 +++-
> 
> MdeModulePkg/Application/UiApp/FrontPageCustomizedUiSupp
> ort.c     | 3 ++-
>  MdeModulePkg/Application/UiApp/UiApp.inf
> | 4 +++-
> 
> .../BootMaintenanceManagerUiLib/BootMaintenanceManagerUi
> Lib.inf   | 4 +++-
> 
> MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootOpt
> ion.c     | 8 +++++++-
>  MdeModulePkg/Library/BootManagerUiLib/BootManager.c
> | 7 ++++++-
> 
> MdeModulePkg/Library/BootManagerUiLib/BootManagerUiLib.i
> nf        | 4 +++-
>  MdeModulePkg/MdeModulePkg.dec
> | 6 ++++++
>  8 files changed, 33 insertions(+), 7 deletions(-)
> 
> --
> 2.14.3.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2018-04-12  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12  1:31 [patch 0/3] MdeModulePkg/UiApp: Signal event when enter/exit setup menu Dandan Bi
2018-04-12  1:31 ` [patch 1/3] " Dandan Bi
2018-04-12  1:31 ` [patch 2/3] MdeModulePkg/BMMUiLib: " Dandan Bi
2018-04-12  1:31 ` [patch 3/3] MdeModulePkg/BMUiLib: " Dandan Bi
2018-04-12  1:44 ` [patch 0/3] MdeModulePkg/UiApp: " Kinney, Michael D
2018-04-12  3:16   ` Bi, Dandan
2018-04-12  3:46     ` Bi, Dandan
2018-04-12  3:49       ` Tim Lewis
2018-04-12  4:53         ` Bi, Dandan
2018-04-12  5:10           ` Tim Lewis
2018-04-12  6:02       ` Zeng, Star
2018-04-12  6:07         ` Bi, Dandan [this message]

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=3C0D5C461C9E904E8F62152F6274C0BB3BAA4ECF@shsmsx102.ccr.corp.intel.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