In the EBBR specifcation we require to use either ACPI tables or a device-tree.
[RFC 00/12] RFC: Devicetree-ACPI hybrid mode
https://lore.kernel.org/linux-acpi/20260623145225.143218-1-johannes.goede@o…
suggests to use a mix of ACPI and device-tree in Linux for better supporting Qualcomm latops.
We may have to revisit our requirement.
Best regards
Heinrich
Dear EBBR stakeholders,
I hope you are all doing well.
We have currently no agenda for our EBBR call today, May 6. [1]
If you have a topic to discuss today, please let us know before 10am UTC,
otherwise we will adjourn the call.
Best regards,
Vincent Stehlé
System Architect - Arm
[1] https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings
Dear EBBR stakeholders,
We have currently no agenda for today's EBBR call. [1]
If you have a topic to discuss today, please let us know before 10am UTC,
otherwise we will adjourn the call.
Best regards,
Vincent Stehlé
System Architect - Arm
[1] https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings
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.
Dear EBBR stakeholders,
We have currently no agenda for today's EBBR call. [1]
If you have a topic to discuss today, please let us know before 10am UTC,
otherwise we will adjourn the call.
Best regards,
Vincent Stehlé
System Architect - Arm
[1] https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings
Dear EBBR stakeholders,
Given that we have no agenda for today [1], let's adjourn this call.
Our next EBBR call will be on Apr 8.
Beware: this call will be on BST time.
Please send discussion topics to the mailing-list (or to me), and submit pull
requests on github.
Best regards,
Vincent Stehlé
System Architect - Arm
[1] https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings
Dear EBBR contributors,
I am happy to announce that v2.4.0 of the EBBR specification has now been
released. [1]
Notable changes since v2.3.0 include changes in the architecture-specific
privileged or secure firmware requirements, a few recommendations and
clarifications, the addition of version annotations and the usual fixes and
references updates.
The following people (listed in alphabetical order) have participated to
this EBBR release directly or indirectly, with patches, github issues, pull
requests, reviews, comments, suggestions, or by participating to the
regular calls:
Achin Gupta
Atish Patra
Bertrand Marquis
Daniel Thompson
Étienne Carrière
François-Frédéric Ozog
Grant Likely
Heinrich Schuchardt
Ilias Apalodimas
Joakim Bech
Jon Humphreys
Michal Šimek
Peter Robinson
Ricardo Salveti
Rob Herring
Vincent Stehlé
A big thank you to all the EBBR contributors!
Best regards,
Vincent Stehlé
System Architect - Arm
[1]: https://github.com/ARM-software/ebbr/releases/tag/v2.4.0
Dear EBBR contributors,
Version 2.4.0-pre3 of the EBBR specification is now available for your
review. A number of fixes have been merged and are now part of the
specification (thanks Heinrich!) Comparisons in text and pdf format are
attached to the pre-release tag. [1]
Please have a look and report any defect you find. In no blocking issue is
reported, we will declare an EBBR v2.4.0 release during our call of Mar 11.
[2]
Thanks!
Vincent Stehlé
System Architect - Arm
[1] https://github.com/ARM-software/ebbr/releases/tag/v2.4.0-pre3
[2] https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings
