Closed paroque28 closed 3 years ago
Yeah, I held off going this far because I don't think this will generalize to any feature that's defined in the linux-yocto metadata... in particular, features that include patches to be applied. Our kernel diverges from upstream significantly in some areas. And I'm not sure how to provide test coverage.
Maybe at some point in the future we could add this to the base recipe, either using the linux-yocto metadata directly, or a fork of our own. In the meantime, you're free to add a bbappend in your distro layer to make use of the metadata if you'd like to.
Hello guys @paroque28 @madisongh
Any update concerning this feature ? Should we close this ticket ?
I think we should close it for now. When Nvidia releases a newer version of the kernel, this will be much easier.
Thanks @paroque28 for your quick feedback. CLosing this ticket
Continuing this commit: https://github.com/madisongh/meta-tegra/commit/29ee143b26af5e1057fb4533a9376ca43512f603#diff-9b732ab86ef3483bb0e54684c28fd84b
We can leverage features from yocto, as an example I am using
systemd.scc
anddocker.scc
and I encounter the following error:This can be fixed with the following patch:
Reference: https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-kernel/linux/linux-yocto_5.4.bb
Build tested in zeus-r32.3.1 for jetson-nano
Thanks, Pablo