Grant, In section 4.2, the /Firmware directory is mentioned. What are the reasons why this new hierarchy of directories are created? Can we not use the existing /EFI hierarchy as shown at http://www.uefi.org/registry? I may have missed the rational when discussed.
If we do need to create a new /Firmware hierarchy, we need to register that with the UEFI Forum as the UEFI Forum owns the ESP name space to avoid conflicts. EBBR cannot single-handedly create new hierarchy. Also, each SoC vendor would need to make request to the UEFI Forum to get their vendor subdirectories under /Firmware as well. - DW - -----Original Message----- From: arm.ebbr-discuss-boun...@arm.com <arm.ebbr-discuss-boun...@arm.com> On Behalf Of Grant Likely Sent: Friday, July 6, 2018 12:13 PM To: boot-architecture@lists.linaro.org; arm.ebbr-discuss <arm.ebbr-disc...@arm.com> Subject: [Arm.ebbr-discuss] EBBR v0.6-pre1 Released I've tagged the prerelease in preparation for a wider v0.6 RFC release next week. Please review and comment: https://github.com/glikely/ebbr/releases/tag/v0.6-pre1 (I've linked to the copy on my personal ebbr fork because I'm having trouble getting Travis-ci to deploy to the official repo. It will take a bit of effort to work out what is wrong) g. _______________________________________________ Arm.ebbr-discuss mailing list arm.ebbr-disc...@arm.com IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ boot-architecture mailing list boot-architecture@lists.linaro.org https://lists.linaro.org/mailman/listinfo/boot-architecture
