On Mon, May 21, 2018 at 1:59 PM, Grant Likely grant.likely@arm.com wrote:
I've been thinking about how to organize EBBR. It started matching the SBBR document structure with the ACPI & ACPI sections removed, but I've moved things around a bit (for instance, citations are now at the end and use the citation markup so they can be collected from the whole document.) We also want to talk about some device sharing issues that SBBR doesn't need to get into, so we need a place to put that stuff.
For discussion, what do you think of the following Table of Contents? I do expect this to change, but I'd like to come to general agreement on how the document is structured.
Looks fine to me, what about optional bits? I'd like to see options around random seed for ASLR and something around secure boot. Not sure where they sit in the uefi spec so where best they'd fit.
Peter
- About this Document
1.1 Introcution 1.2 Scope
- UEFI
2.1 UEFI Version 2.2 UEFI Compliance 2.3 UEFI System Environment and Configuration 2.4 UEFI Boot Services 2.4.1 Required (Moved from Appendix to here) 2.4.2 Optional (this section may be redundant. If it isn't required, then by default it is optional!!) 2.5 UEFI Runtime Services 2.5.1 Required 2.5.2 Optional
- System Configuration Data
3.1 Devicetree 3.2 ACPI
- Privileged Firmware
4.1 PSCI 4.2 Secure Services
- Hardware Configuration and Access
5.1 Shared Storage Media 5.1.1 Block device partitioning 5.1.2 Protecting firmware partitions/blocks 5.2 Shared access (i2c/SPI) 5.3 RTC
(Everything below is additional guidance material, and doesn't make up part of the spec. I've not decided if I'd rather have it in the documentm, or as a separate guidance note) Appendix A - U-Boot implementation note (How to configure U-Boot to be EBBR compliant) Appendix B - EBBR Compliance Testing _______________________________________________ Arm.ebbr-discuss mailing list Arm.ebbr-discuss@arm.com