-
Notifications
You must be signed in to change notification settings - Fork 37
EBBR Notes 2018.05.10
Grant Likely edited this page May 15, 2018
·
1 revision
- Ryan Harkin (Linaro)
- Grant Likely (Arm)
- Bill Mills (TI)
- Tom Rini (Konsulko)
- Peter Robinson (Red Hat)
- Daniel Thompson (Linaro)
- Dong Wei (Arm)
- Leif Lindholm (Arm)
- Udit Kumar (NXP)
- Action item review
- Any other business
- Recommended policy on shared devices (Bill)
- Conversation occurring on mailing list - discussion still needed
- Write policy on shared media (Leif)
- Conversation occurring on mailing list - no consensus yet.
- Leif: What platforms are we trying to support? The behaviour today, or what we want?
- Daniel: Persistent variables behaviour (whether or not variables are shown on when setVariable() is not available at runtime) seems to be all
- Leif: Should have guidance notes on how we expect operating systems to behave
- Bill: Still need to talk about defining how to share eMMC
Action Daniel to create a scratchpad roadmap of what goes in Level 0, 1, 1+
- Level 1/1+: EBBR can impose requirements on the boot ROM?
- Level 1/1+: DT overlays (scope depends on best technical approach to apply/unapply them, could come into scope if OS is provided an interface to do this)
- Is it just the contract between the OS and the firmware?
- Or is it okay to have examples in the document?
- Leif: totally okay with that
- Grant: I'm totally okay with that too
- MBR is back - complete consensus
- Some disagreement about protective partitions
- ESP containing firmware [level 1+ ;-) ] allows live boot images even for boards where OS and firmware reside on the same removeable media.
- Level 0: Board specific EBBR SD card + boot generic OS installer from (really) removeable media
- Level 1: Generic EBBR SD card for multiple boards + EFI netboot application ;-)