Hi Grant Few comments
1/ 1.1 Introduction >For example, an Arm A-class embedded networking platform to >For example, an Arm A-class embedded platform 2/ 1.2 Guiding Principals >EBBR as a specification defines requirements to >EBBR as a specification define requirements 3.1/ 1.3 Scope Please see, if we can remove reference to SBBR here. In case, we wish to put this reference then SBBR does not may about hardware requirement >with SBBR having stricter requirements on hardware to >with SBSA having stricter requirements on hardware 3.2/ 1.3 Scope Below may not be a valid example, SBBR recommends to use sperate storage but does not mandate it. In other discussion Dong Wei said this is left on implementation >For example, an embedded system may use a single eMMC storage device >to hold both firmware and operating system images 4/ 2.4.3 Configuration Tables >A UEFI system that complies with this specification may provide the additional >tables via the EFI Configuration >Table. Please help with some example tables here. >As stated above, EBBR systems must not provide both ACPI and Devicetree tables >at the same time. Systems that >support both interfaces must provide a configuration mechanism to select >either ACPI or Devicetree Could we reword this please, first we said, either ACPI or devicetree. Later we are saying selection to be done. Also at what time, ACPI or devicetree to be selected build time or runtime 5/ FIRMWARE STORAGE Please elaborate ESP at first place, this is used instead of doing this later > of the storage used for OS partitions and the ESP To > of the storage used for OS partitions and the ESP (EFI System Partition) 6/ 4.1 Partitioning of Shared Storage > Warning: > A future issue of this specification will remove the MBR We are putting a requirement on hardware here. Do we want to update boot ROM to understand GPT in future hardware ? 7/ 5.2 Required Runtime Services Please add a note for Update capsule too, Similar to Get/Set Time, Update capsule can return EFI_UNSUPPORTED Regards Udit > -----Original Message----- > From: arm.ebbr-discuss-boun...@arm.com [mailto:arm.ebbr-discuss- > boun...@arm.com] On Behalf Of Grant Likely > Sent: Saturday, July 7, 2018 12:43 AM > 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://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub. > com%2Fglikely%2Febbr%2Freleases%2Ftag%2Fv0.6- > pre1&data=02%7C01%7Cudit.kumar%40nxp.com%7Ccc2fd094bcb9462f79 > 8908d5e3747e4a%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6366 > 65011834763051&sdata=or0ngRAQ937f37XgY8vUPFEaX86YigH2a5J122v98 > z0%3D&reserved=0 > > (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 _______________________________________________ boot-architecture mailing list boot-architecture@lists.linaro.org https://lists.linaro.org/mailman/listinfo/boot-architecture
