In 4.4 of BBR when discussing LBBR recipe we do provide a note to point to the OSF checklist. However, SystemReady is not the place to require it. Arm supports both open and commercial firmware.
Sent from my iPhone > On Oct 25, 2021, at 6:44 AM, François Ozog <francois.o...@linaro.org> wrote: > > Hi > > back in April we had a workshop on firmware sustainability. Since then a > number of discussions related concerns on closed source components in TF-A > and U-Boot communities. We are also approaching a technical maturity level > on SystemReady that it looks timely to revisit this aspect. > > Would it be a good move to adopt the Open System Firmware check list > <https://www.opencompute.org/wiki/Open_System_Firmware/Checklist> as part > of SystemReady? > > *NOTE1: believe SystemReady is at right level as it addresses compliance > of platforms. EBBR is a technical recipe to make it work for a particular > environment (like SBBR) and so not the best place to deal with > redistribution license of binary blobs and other platform owernship > aspects.* > > *NOTE2/ Adoption could come in different forms: referring to it, crafting a > similar one for SystemReady scope, any other smart ways of doing it.* > > > Cheers > > FF > > -- > François-Frédéric Ozog | *Director Business Development* > T: +33.67221.6485 > francois.o...@linaro.org | Skype: ffozog > _______________________________________________ > boot-architecture mailing list > boot-architecture@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/boot-architecture 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. _______________________________________________ boot-architecture mailing list boot-architecture@lists.linaro.org https://lists.linaro.org/mailman/listinfo/boot-architecture
