The current RMC project provides 3 APIs and 2 libraries for clients in UEFI and Linux user space context. I think we can refactor the project to have just 1 API and library (built respectively for UEFI and user space), so that necessary logic for RMC in clients is minimized.
I have had patches to support single libraries. I am working on a big patch to provide APIs in rmc project.
I have submitted a big patch series to yocto mailing list. The submission includes this task and more enhancements: () Simplify two libs into one for each context, Linux or EFI (this bz10086) () Provide APIs for clients. They can use either single API to perform a query or use two APIs to perform mulitple queries for a better runtime performance. (this bz10086) () Remove dependency to gnu-efi in EFI build () No need to tell EFI arch in rmc build anymore () Remove the obsolete data type and usage for kernel cmdline () Misc. fixes in Makefiles and source code. I anticipate to receive multiple feedbacks from the community, given the huge size of the series. Update my estimation for the remained actions: () follow-up any feedbacks on the patch series. () Submit another patch series in meta-intel once the submission is merged in rmc project: - update rmc recipe to the latest rmc revision and cleaning up - remove gnu-efi from meta-intel. We don't have to carry it any more -
I have submitted a patch series to meta-intel mail list to update rmc and other pieces in meta-intel to make these works effective today.
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=58e5069ee34edd585ca11dfa387bd122d45995aa http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=b01ba818906dd685db9147916f535e70ba2f4d9f The patch series has been merged in meta-intel. Close it as fixed.