thesofproject
Loadable up down mixer
@pjdobrowolski are you using a 3rd party binary for the mixer OR just the code we have in the SOF repo? Or, does it matter?
@pjdobrowolski are you using a 3rd party binary for the mixer OR just the code we have in the SOF repo? Or, does it matter?
This is the example how to convert up_down_mixer from SOF repo to loadable version. Only requirement for conversion is to set UPDWMIX to know in configuration to exclude up_down_mixer from build_in modules.
Changed to draft, module will be moved to https://github.com/thesofproject/converged-sof-modules
Changed to draft, module will be moved to https://github.com/thesofproject/converged-sof-modules
No, this repo was temporary and for staging only prior to module API, IPC4 etc being upstream in main. All the dependencies are now upstream so all library support should go upstream. We also cannot duplicate our modules in two places.
This repo will be moving to archived state, there is no need to keep it today.
Ok, I removed all unnecessary MODULE_PRIVAT tags and created exported headers from sof. Now up_down_mixer is building outside of sof. @softwarecki now we must create some kind of git/python verification script to check if these headers change or what happen with them for ABI verification.
please check https://github.com/thesofproject/sof/pull/8554. We don't need to copy headers to lmdk.
llext and native loadable modules are not the same.
@pjdobrowolski what @RanderWang is talking about isn't an LLEXT module, it's what you call a "native" system-service module, that he has submitted, you still don't need to copy headers for those
