Sound Open Firmware
TSC Meeting August 2022 #7402
Replies: 15 comments
-
|
@lgirdwood https://doodle.com/meeting/participate/id/dNxZqPpa Let's see if we can meet next week. |
Beta Was this translation helpful? Give feedback.
-
|
@thesofproject/amd @thesofproject/mediatek pls register your availability and suggest topics for discussion and alignment. |
Beta Was this translation helpful? Give feedback.
-
|
@thesofproject/amd @thesofproject/google @thesofproject/intel @thesofproject/mediatek @thesofproject/nxp Thursday 3 - 4PM GMT is so far looking like the best time. Will send invite out tomorrow AM UK time to give time for final topics and availability. |
Beta Was this translation helpful? Give feedback.
-
Thanks, Done from AMD |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will inform our menbers of date. (MediaTek) |
Beta Was this translation helpful? Give feedback.
-
Didn't receive the meeting invite, meeting is there today? |
Beta Was this translation helpful? Give feedback.
-
|
@bhiregoudar what is your email address i can forward it to you |
Beta Was this translation helpful? Give feedback.
-
|
HI Daniel, @dbaluta We didn't receive the meeting invite either. |
Beta Was this translation helpful? Give feedback.
-
@kuanhsuncheng please check email now. We need to sync better for the next meetings :) |
Beta Was this translation helpful? Give feedback.
-
|
Here how to meeting shows in my calendar. Note that time is in Eastern European Time zone.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
You sure this is ok?
|
Beta Was this translation helpful? Give feedback.
-
sorry, it is basavaraj.hiregoudar@amd.com |
Beta Was this translation helpful? Give feedback.
-
|
We see the meeting invite, thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @dbaluta - we need to gather a list of emails for next time. GH usernames don't work for meetings ! |
Beta Was this translation helpful? Give feedback.
-
@thesofproject/steering-committee Now that most members are back from summer holidays and v2.2 was released in early summer lets look forward and align on v2.3 features and v2.4 planning.
Register your availability: https://doodle.com/meeting/participate/id/dNxZqPpa
Agenda please add/edit items.
Zephyr update and status. Next steps.
IPC4 and Windows support.
Old Intel platform deprecation. Intel plans to park some older HW at v2.2
RTOS partitioning. Partitioning the codebase for clean separation of rtos code from common code.
Tooling update - Integrating with Zephyr and Windows based tools.
Separate repos for tooling and topologies - Using "west" now permits alignment of multiple repos and means its easier to release updates for topologies and tools without a FW release.
Enroll SOF to become Open Source Security Foundation (OpenSSF)
compliant project like Zephyr - see Zephyr example https://bestpractices.coreinfrastructure.org/en/projects/74
Beta Was this translation helpful? Give feedback.
All reactions