So, the impact is every platform DSC needs to be updated to reference the correct path of the UefiDevicePath lib after your merge.
Let's wait for at least 2 weeks for feedbacks. Thanks, Ray From: Gao, Zhichao <[email protected]> Sent: Friday, January 10, 2020 3:47 PM To: Ni, Ray <[email protected]>; [email protected]; '[email protected]' <[email protected]> Cc: Gao, Liming <[email protected]>; Kinney, Michael D <[email protected]>; [email protected] Subject: RE: [RFC] BZ 2298 MdePkg/DevicePathLib merger or not Ray, I prefer to merge these two lib instance into one folder and remove the duplicated code. I can change all the required change in open source repo. But not sure how many close source platforms would be affected. This action should make all the close platform owners aware of it and changing their platform code to consume the new lib instance. #2: OK. That makes sense to consume the new device path node if appear. Thanks, Zhichao From: Ni, Ray Sent: Friday, January 10, 2020 3:36 PM To: Gao, Zhichao <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: Gao, Liming <[email protected]<mailto:[email protected]>>; Kinney, Michael D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [RFC] BZ 2298 MdePkg/DevicePathLib merger or not Zhichao, What's your recommendation regarding this? Back to your 2nd question, drivers/applications consuming UefiDevicePathLibOptionalDevicePathProtocol can firstly use the firmware built-in from-text and to-text conversion, then use its own conversion logic if the firmware doesn't contain built-in from-text or to-text conversion. Considering a case that an application is released in year 2015, it can recognize the new device path node introduced after 2015 in a new system. Thanks, Ray From: Gao, Zhichao <[email protected]<mailto:[email protected]>> Sent: Friday, January 10, 2020 11:04 AM To: [email protected]<mailto:[email protected]>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: Gao, Liming <[email protected]<mailto:[email protected]>>; Kinney, Michael D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Ni, Ray <[email protected]<mailto:[email protected]>> Subject: [RFC] BZ 2298 MdePkg/DevicePathLib merger or not HI all, REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2298 In the MdePkg, there are two folder for the DevicePathLib: 1. MdePkg\Library\UefiDevicePathLib 2. MdePkg\Library\UefiDevicePathLibDevicePathProtocol UefiDevicePathLibDevicePathProtocol is created to use the protocol to reduce the driver size which consume the DevicePathLib. But it has duplicate code with #1. So I want to merge these two folder into one. But many platform implementations consume #2. If we merge #2 into #1, there might be a lot of platform changes for both close source and open source. Can anyone give me some suggestions about this? Do we have a progress to retire some implementation in the edk2 repor? There is another question about MdePkg\Library\UefiDevicePathLib\UefiDevicePathLibOptionalDevicePathProtocol.inf. This one implements the interface to choose the protocol first, then change to local implementation if no protocol is available. It requires a fix and it is already sent to the community. But what's the purpose? Local implementation, i.e. MdePkg\Library\UefiDevicePathLib\ UefiDevicePathLib.inf, can make sure its usable. And it can't reduce the driver size. If it is useless, can we directly remove it? Thanks, Zhichao -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#53148): https://edk2.groups.io/g/devel/message/53148 Mute This Topic: https://groups.io/mt/69593973/21656 Group Owner: [email protected] Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
