Guennadi Liakhovetski

@marc-hb right, the error message comes out misleading. `sparse` isn't installed. As explained, you have to install it manually in your docker image from git. For an explanation (and eventual...

> Thanks @nklayman , good catch. > > @lyakh, from the top of your head could you share a quick and barely tested set of commands that would build sparse...

> @lyakh I guess you use the default Zephyr SDK gcc `xtensa-intel_s1000_zephyr-elf-gcc` to build zephyr with Sparse. The default gcc also works for me without errors. The above errors are...

> 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...

> @lyakh Really don't know what to do with the sparse checks? It's not really sustainable for SOF to check for things not done in Zephyr. Can we limit these...

> This is not valid for i.MX where the TEXT or BSS sections are _NOT_ contiguous: Sorry, I don't know details of your platform. How do you load your firmware...

> @lyakh where was this problem detected, CI or your local setup? @plbossart it was in my own setup

the best would be of course if we could re-use CMakeLists.txt in subdirectories for both XTOS and Zephyr. If this is impossible, we could move XTOS specific code to xtos.cmake,...

@softwarecki one question: have you tested these patches with llext and in particular with the scenario that you are trying to fix - with multiple pipelines? If not, let's put...

> @lyakh Don't treat it like a real PR. I created it just to show my vision of where I thought the zephyr llext handle should be stored. The `module_data`...