...
Filled from Google Meet report
Slides
Notes
LR: What’s the main purpose of the MbedOS work vs SDFX API?
MS: Starting point of APIs is MbedOS HAL version xx.yy. If want to propose changes they are welcome
ED: Team is busy on testing at the moment. Will bring back the discussion about e.g. SDFX API
KG: Any reason to not to allow discussing on SDFX API.
CG: (to QS) Can you check if the access to CI repos is public?
QS: Should be public. Not under Arm Mbed org - but under MCU-Driver Hal. Please could you check again
PS: (via chat) https://github.com/MCU-Driver-HAL/MCU-Driver-HAL-CI-ENV seems accessible without GitHub login
ED: Can close on maintenance processes next week
PS: Any updates on SDFX-architecture repository which hosts current documentation?
ED: Need to decide where we want to host the documentation - to be decided.
KG: What about contributions in the next couple of weeks
ED: ST and NXP repositories are under their control
KG: Non silicon support - what’s the process for that to get reviewed?
ED: Can always raise a pull request and it’s case-by-case.
KG: Feels like we don’t have a clear process (since don’t normally know who is contributing what when). Feels like contributing outside of SoC scope
ED: For more complicated cases agree it’s better to hold off for now
BJ: The demo with serial/vtable is available?
MS: Will bring a proposal soon on how to test a new API with greentea