From: Felix Poludov <Felixp@ami.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] MdePkg: UiLib library
Date: Thu, 10 Nov 2016 13:37:34 +0000 [thread overview]
Message-ID: <9333E191E0D52B4999CE63A99BA663A00270FF9E17@atlms1.us.megatrends.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50386CDB6E@shsmsx102.ccr.corp.intel.com>
Hi Jiewen,
Updating "all the code that uses the old API to use the new API" is not always possible.
We can certainly update all the EDKII packages; however, it is trickier with the non-open source packages.
For example, the Reference Code we are getting from a chipset vendor is using CreatePopUp.
Certainly, if we mark CreatePopUp deprecated (as you have suggested), the chances are, reference code will get eventually updated not to use the function.
However, it might take a significant amount of time.
Moreover, a project integrators that create board firmware by combining open-source and close-source packages coming from multiple sources(from multiple vendors),
would have to solve this issue again and again; whereas with my proposal, the issue is solved by upgrading EDKII code base (no need to touch third party packages).
Having said that, I do understand your concerns with keeping the library in MdePkg.
How about finding a middle ground between your proposal and my proposal?
We can keep UiLib instance in MdePkg, but keep only a minimalistic barebones implementation there.
We can also have another, more advanced, UiLib instance in the MdeModulePkg.
This technique is already used in EDKII.
For example, MdePkg defines DebugLib library class and provides BaseDebugLibSerialPort instance.
MdeModulePkg provides PeiDxeDebugLibReportStatusCode instance for the same library class.
Since "advanced" version of Popup is not currently available, there is no need to create new instance in MdeModulePkg.
However, once Eric is ready with his Popup-on-top-of-HII implementation, it can be added to a new UiLib instance in MdeModulePkg.
Also, if new functions are added to UiLib in the future, MdePkg UiLib instance can have a NULL implementation like many other libraries in the MdePkg.
What do you think?
Thanks
Felix
From: Yao, Jiewen [mailto:jiewen.yao@intel.com]
Sent: Wednesday, November 09, 2016 8:54 PM
To: Felix Poludov; edk2-devel@lists.01.org
Subject: RE: [PATCH 0/2] MdePkg: UiLib library
HI Poludov
It is a good idea to have a new UiLib.
Both Mike and I give the suggestion to "You could define new lib and update all the code that uses the old API to use the new API."
IMHO, I do not think it is right way to let UefiLib depend on a UiLib.
We have plan to resolve it, but since you already have proposal to add UiLib. I hope it can be resolved here.
There is no real need to put UiLib into MdePkg. MdePkg is designed to hold EFI/PI speciation or industry standard.
In this case, I believe MdeModulePkg is a better place.
Thank you
Yao Jiewen
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Felix Poludov
> Sent: Wednesday, November 9, 2016 11:44 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/2] MdePkg: UiLib library
>
> This series of two patches introduces new UiLib library.
> 1. New UiLib library class is added to MdePkg.
> The library is intended for functions that produce UI elements.
> The patch introduces two functions that produce a popup window:
> UiCreatePopUp and UiCreatePopUpVaList.
> 2. An instance of UiLib library class is added to MdePkg.
> Popup implementation is copied from UefiLib
> (CreatePopUp function in UefiLib/Console.c).
> 3. MdePkg/UefiLib library is updated to implement CreatePopUp
> by calling UiCreatePopUpVaList.
> 4. Platform DSC files are updated to add UiLib instance.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Felix Polyudov <felixp@ami.com>
>
> AppPkg/AppPkg.dsc | 1 +
> ArmPkg/ArmPkg.dsc | 1 +
> BeagleBoardPkg/BeagleBoardPkg.dsc | 1 +
> CorebootPayloadPkg/CorebootPayloadPkgIa32.dsc | 1 +
> CorebootPayloadPkg/CorebootPayloadPkgIa32X64.dsc | 1 +
> CryptoPkg/CryptoPkg.dsc | 1 +
> DuetPkg/DuetPkgIa32.dsc | 1 +
> DuetPkg/DuetPkgX64.dsc | 1 +
> EdkCompatibilityPkg/EdkCompatibilityPkg.dsc | 1 +
> EmbeddedPkg/EmbeddedPkg.dsc | 1 +
> EmulatorPkg/EmulatorPkg.dsc | 1 +
> FatPkg/FatPkg.dsc | 1 +
> .../IntelFrameworkModulePkg.dsc | 1 +
> IntelFsp2WrapperPkg/IntelFsp2WrapperPkg.dsc | 1 +
> IntelFspWrapperPkg/IntelFspWrapperPkg.dsc | 1 +
> MdeModulePkg/MdeModulePkg.dsc | 1 +
> MdePkg/Include/Library/UiLib.h | 71 +++++
> MdePkg/Library/UefiLib/Console.c | 252
> +---------------
> MdePkg/Library/UefiLib/UefiLib.inf | 1 +
> MdePkg/Library/UefiLib/UefiLibInternal.h | 1 +
> MdePkg/Library/UiLib/UiLib.c | 334
> +++++++++++++++++++++
> MdePkg/Library/UiLib/UiLib.inf | 38 +++
> MdePkg/Library/UiLib/UiLib.uni | 21 ++
> MdePkg/MdePkg.dec | 3 +
> NetworkPkg/NetworkPkg.dsc | 1 +
> Nt32Pkg/Nt32Pkg.dsc | 1 +
> Omap35xxPkg/Omap35xxPkg.dsc | 1 +
> OptionRomPkg/OptionRomPkg.dsc | 1 +
> OvmfPkg/OvmfPkgIa32.dsc | 1 +
> OvmfPkg/OvmfPkgIa32X64.dsc | 1 +
> OvmfPkg/OvmfPkgX64.dsc | 1 +
> PcAtChipsetPkg/PcAtChipsetPkg.dsc | 1 +
> PerformancePkg/PerformancePkg.dsc | 1 +
> QuarkPlatformPkg/Quark.dsc | 1 +
> QuarkPlatformPkg/QuarkMin.dsc | 1 +
> QuarkSocPkg/QuarkSocPkg.dsc | 1 +
> SecurityPkg/SecurityPkg.dsc | 1 +
> ShellPkg/ShellPkg.dsc | 1 +
> SourceLevelDebugPkg/SourceLevelDebugPkg.dsc | 1 +
> StdLib/StdLib.dsc | 1 +
> UefiCpuPkg/UefiCpuPkg.dsc | 1 +
> Vlv2TbltDevicePkg/PlatformPkgGccX64.dsc | 1 +
> Vlv2TbltDevicePkg/PlatformPkgIA32.dsc | 1 +
> Vlv2TbltDevicePkg/PlatformPkgX64.dsc | 1 +
> 44 files changed, 506 insertions(+), 251 deletions(-)
> create mode 100644 MdePkg/Include/Library/UiLib.h
> create mode 100644 MdePkg/Library/UiLib/UiLib.c
> create mode 100644 MdePkg/Library/UiLib/UiLib.inf
> create mode 100644 MdePkg/Library/UiLib/UiLib.uni
>
> Please consider the environment before printing this email.
>
> The information contained in this message may be confidential and
> proprietary to American Megatrends, Inc. This communication is intended
> to be read only by the individual or entity to whom it is addressed or by their
> designee. If the reader of this message is not the intended recipient, you are
> on notice that any distribution of this message, in any form, is strictly
> prohibited. Please promptly notify the sender by reply e-mail or by
> telephone at 770-246-8600, and then delete or destroy all copies of the
> transmission.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
Please consider the environment before printing this email.
The information contained in this message may be confidential and proprietary to American Megatrends, Inc. This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
next prev parent reply other threads:[~2016-11-10 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 15:43 [PATCH 0/2] MdePkg: UiLib library Felix Poludov
2016-11-10 1:53 ` Yao, Jiewen
2016-11-10 13:37 ` Felix Poludov [this message]
2016-11-10 15:10 ` Gao, Liming
2016-11-10 15:44 ` Felix Poludov
2016-11-10 16:02 ` Gao, Liming
2016-11-10 16:04 ` Kinney, Michael D
2016-11-10 16:11 ` Felix Poludov
2016-11-10 16:18 ` Gao, Liming
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=9333E191E0D52B4999CE63A99BA663A00270FF9E17@atlms1.us.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