Replies: 1 comment 2 replies
-
Depending on how extensive your changes are going to be, it might be simpler to just fork the linux-tegra repo and create a branch with your modifications on it. It's easy to add a bbappend file for the linux-tegra recipe to have it point to your repo, branch, and SRCREV. That's what I do in my projects. The Yocto documentation is more oriented towards the Yocto Project-hosted kernel, which combines sources from one repo with sets of config fragments and patches from another based on the target platform, which adds some complications to the process. None of that is necessary here. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I'm pretty new to the whole yocto thing but we're trying to develop something using the xavier/orin, and for this we need to add some of our own drivers and more generally just be able to develop on this kernel, but I'm a bit stuck on how to best go about this.
Currently we already build a tegra-demo image with some extras to get our application running and so far so good.
Would following these steps but changing linux-yocto to linux-tegra suffice?
https://docs.yoctoproject.org/kernel-dev/common.html#getting-ready-for-traditional-kernel-development
https://docs.yoctoproject.org/kernel-dev/common.html#using-traditional-kernel-development-to-patch-the-kernel
Or what would be the best way to go about modifying the jetson kernel or figuring out how it works? Because the whole patchwork of modified makefiles and overlays can be pretty confusing.
Thanks in advance,
Jesse
Beta Was this translation helpful? Give feedback.
All reactions