Hi, John -

I was indeed able to successfully execute Robert's instructions, so I know 
how to make the kernel. Useful information for when the time comes for it. 
I will also note your advice above. Very much appreciated.

This thread has drifted a bit, and so I think I'll close it out. I'll 
pursue my original question (how to cross build and debug an LKM) in 
another forum, since I think I've bugged everyone here enough for now.

Thanks to all who participated in this thread...

On Tuesday, June 27, 2017 at 6:44:08 PM UTC-6, john3909 wrote:
>
> I see Robert has answered all your question. Here are some suggestions 
> that might help once you complete the first build. 
>
> After you build, you will find the kernel on the yakbuild/KERNEL folder. 
> This is where you edit your code. Do not “build_kernel.sh” again as this 
> will overwrite any code you edited. Use yakbuild/tools/rebuild.sh to 
> rebuild the kernel with your changes. The output of the build is placed in 
> the yakbuild/deploy folder. You will find an yakbuild/deploy/update.sh 
> which you can customize to copy the files to your NFS share or use 
> yakbuild/deploy/updateSD.sh to update your BBB SDcard.
>
> I recommend that you place your kernel module/driver under the 
> yakbuild/KERNEL/drivers folder. If you create a custom folder, then you 
> need to edit the Makefile and Kconfig files in the drivers folder. Your 
> custom folder must also have a Makefile and Kconfig file. Look at other 
> folders in the drivers folders for examples. 
>
> Alternatively, you could also use the yakbuild/KERNEL/samples folder for 
> your source code. 
>
> Regards,
> John
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4646b453-2069-4d7a-a0f8-30f487caaf98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to