David, That will cause confusion to caller of *GetBootOption(). Because two behaviors will be seen: 1. BdsDxe calls this API to get a platform customized name for a certain option. 2. Another module calls this API to get a "Misc" name for a certain option because it doesn't link to PlatformBootManagerLib.
Wait a sec, perhaps I am over worried. If the NULL class library calls *Register* API, then any consumer of *GetBootOption() API can link that NULL class library so the consistent boot description can be achieved. But I still need to understand why the *GetBootOption() API is needed. Because for quite a long time since the MdeModulePkg/Bds was added, there is no such requirement. Thanks, Ray > -----Original Message----- > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of David > Woodhouse > Sent: Tuesday, June 25, 2019 4:29 PM > To: devel@edk2.groups.io; Ni, Ray <ray...@intel.com>; ler...@redhat.com > Subject: Re: [edk2-devel] [PATCH 6/7] MdeModulePkg/UefiBootManagerLib: > describe VirtIO devices correctly > > On Tue, 2019-06-25 at 08:06 +0000, Ni, Ray wrote: > > The *Register* API was invented to handle the situation that platform > wants > > to have a special name for certain boot options. > > I think you can use that. > > Except didn't I just agree to stop calling those registered handlers > from the exported EfiBootManagerGetBootDescription() function, because > of the transitive dependencies? > > -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#42799): https://edk2.groups.io/g/devel/message/42799 Mute This Topic: https://groups.io/mt/32163533/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
