Adrian Warecki
Adrian Warecki
@RanderWang yeah, that's right! I didn't do it right away because another colleague was expanding a functionality od the mixin/mixout at that time. At the moment I'm on the turbo...
@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` structure...
@dbaluta: > @softwarecki what is `native loadable modules`? We currently have three types of loadable modules... 1. IADK supported by Processing Module Aadapter, 2. native supported by lib_manager 3. llext...
@lyakh Can you check do it still breaks llext?
> @softwarecki why do you think it's fixed now? What's been changed compared to that version? I compared and I don't see any changes that would fix it. `buildinfo` is...
@lyakh The `buildinfo` structure is not propagated up because there is no need for it. For llext modules it is retrieved in the `llext_manager_link` function and checked in `llext_manager_allocate_module` (see:...
Rebased and applied @lyakh patch.
@lyakh In a situation where a preferred buffer size given by the IPC is too large to be allocated, the size of a buffer is reduced step by step until...
@lyakh Let me explain. For example, we want to make two allocations (min=16k, preferred=128k) but we only have 96k available. In the case of a classic allocation using `sys_heap`, we...
@lyakh Fragmentation applies only to the virtual address space. For example, if for a 48k buffer, vmh allocated a 64k buffer then only a 48k of physical memory will be...