-
Notifications
You must be signed in to change notification settings - Fork 37
EBBR Notes 2020.09.28
- Joakim Bech (Linaro)
- Mark Brown (Linaro)
- Ruchika Gupta (Linaro)
- Grant Likely (Arm)
- Daniel Thompson (Linaro)
- Heinrich Schuchardt
- Simon Glass (Google)
- Matthias Brugger (SUSE)
- Issue & PR review
- Secure Platform Requirements -- way forward?
- Storage location of DT -- Heinrich
- Changes to DT spec
- Next release planning
- DT Spec changes; discuss here?
- Any other business
#55: Prefer to handle via DT spec if possible. Similar wording proposed for DT spec (and quick side-by-side during meeting looks OK).
#47: How much, if any, of secure platform requirements to we want in scope for EBBR? Can always split out at a later stage.
#56 & #57: Reminders after mailing list discussion. Still waiting for patches...
#58: Storage location of device trees. Still expect firmware to provide a default DTB. However perhaps standardizing a tools to help navigate unstable DTs (e.g. when distro wants to provide updated DTs whether they can merge). "Prefered design is not to have unstable DT evolution". Custom EFI boot service to provide fixups (would allow grub to fetch a DT from root/bootfs and apply firmware knowledge)? No consensus at this stage!
0.4 DT spec is brewing, will include text from pr #55 above.
Time based releases? Feature driven releases?
RISC-V PRs should provoke a release a sensible time after merging.