Notes from this week's meeting

This was a kickoff meeting where we discussed what EBBR is intended to be. I've showed a few slides which can be found here:

https://drive.google.com/file/d/1p-v5OQ5tNGjxipaPB8AcOKNxues9c6YJ/view?usp=s...

Attendees (Skype said 13 people joined, but I didn't get quite that many names.): - Nicusor Penisoara (NXP) - Udit Kumar (NXP) - Bill Mills (TI) - Rob Herring (Linaro) - Tom Rini (Konsulko) - Grant Likely (Arm) - Peter Robinson (Red Hat) - Daniel Thompson (Linaro) - Nicolas Dechesne (Linaro) - Alex Graf (SuSE) - Michal Simek (Xilinx)

We talked about the target audience for EBBR and how the project would progress. Below are some of the notes I captured on comments and questions.

From Tom: - We need to start writing down a list of requirements - It would be useful to have a reference implementation - Bill added: Was discussed at Connect, and it would be good to have a QEMU configuration as one of the reference implementations.

Udit: - Will there be a compliance test suite? - Tom: He will happily add any test cases to the U-Boot CI loop - Bill: U-Boot CI testing is far more useful to him than a formal test suite

Bill: - I want this forum (EBBR) to be the place to dicuss things that all the vendors are doing, but doing in different ways. Want's to start defining common architecture.

Daniel: - Would like EBBR to Encourage sanity in SoC masked-boot roms - Not feasible for EBBR Level 0 (because it will use existing hardware) but should provide guidance for future SoCs. - Bill: Be aware that it may take 5 years before recommendations appear in silicon

Udit: - EBBR Should include a section on minimum hardware requirements

Peter: - Would like EBBR to cover both aarch32 and aarch64 - Alex concurs - General agreement that EBBR could be applicable to more than just Arm, - Arm is the driver on this, but there is nothing that excludes other architectures. - EBBR depends on other specs (ex. UEFI) to define ABI. Those specs will need to cover an architecture considered to be included in EBBR - Udit - Big Endian platforms like PowerPC may be a problem - UEFI doesn't support big-endian

Alex: - Big question: how do we make sure devicetrees are compatible?

Actions: - [Dong] Work out with Arm ATG the EBBR ownership and release process - [Grant] Set up repository for holding EBBR repo, issue tracker, and wiki - [Grant] Create skeleton document to start capturing requirements.

On 05/04/2018 12:06, Grant Likely wrote:

Time: Every Thursday at 16:30-17:30 BST (8:30 PDT, 23:30 CST) Join by Phone +44 2033215213,, 4664465# https://meet.lync.com/armh/grant.likely/YBY93TIK

This is a weekly status call for the EBBR drafting process that came out of a discussion at Linaro Connect HKG18 in March this year. As mentioned in the notes[1] from that meeting, there is a desire to have EBBR published in time for it to be used by an upcoming 96Boards specification, due to be released in about 6 months time. This meeting is a regular status update to track progress on EBBR development. I will endeavour to keep it short when there isn’t much to discuss. I expect initially there will be a lot to discuss to get the ball rolling, and then will taper off.

Anyone is welcome to join. Feel free to pass this invitation along. Let me know if anyone has trouble dialling/connecting to the SfB bridge.

[1] https://lists.linaro.org/pipermail/boot-architecture/2018-April/000419.html

---

Join online meeting https://meet.lync.com/armh/grant.likely/YBY93TIK

Trouble Joining? Try Skype Web App https://meet.lync.com/armh/grant.likely/YBY93TIK?sl=1

Join by Phone +44 2033215213,, 4664465#

Find a local number https://dialin.lync.com/7bdb65cd-97d0-44fe-bc03-bf8072eadc33 Conference ID: 4664465

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.