> On Fri, May 29, 2026 at 5:28 PM Alexandre Courbot <[email protected]> wrote: >> >> In the meantime, this series introduces a Nova-local workaround for >> `nova-drm` to call into `nova-core`. It generates the `nova-core` >> metadata that `nova-drm` can use to resolve references at build-time, >> and also builds a list of exported symbols for symbol resolution when >> modules are loaded. > > The "local approach" is essentially what I suggested back then, so if > this works for you then I am happy -- with the understanding that we > will replace it with the global support soon (it is good to have a use > case in-tree :)
Yup, I just want to have something that allows us to call from `nova-drm` to `nova-core` as it becomes increasingly pressing for us to be able to do so, but will be very happy to replace this with the global support as soon as it is available. This patchset won't make it for the 7.2 merge window, so if support in the R4L build system comes during the next cycle we may even be able to skip this altogether. > > I see you play some tricks to get the ordering right, including a > sub-make with a double build of the `.rmeta` in "private", which in > turn forces you also to do the `.o`, right? > > What I originally had in mind was simply to do everything from a > single parent `Makefile` instead, precisely to avoid complexity (after > all, it is the local approach, so you don't need to force yourself to > handle that). That should remove all those shenanigans, and it is way > easier to get right. Did you consider it? I haven't thought about that, no - in that case the parent `Makefile` would need to be the one in `drivers`? Or am I missing something? > > By the way, I think a `.gitignore` entry for the generated header is missing. Thanks, I'll add that.
