Hi there,

 

I am a newbie. Just built my first kerne;/uboot for my RockPi S board.

 

I was wondering a few things :

* Are the kernel sources online ? For example :  linux-source-5.9.16-rockchip64.tar.xz

* If I want to add a devicetree overlay and driver code, what is the best way to do that ? Should I ammend the kernel ? Should I create an out of kernel package ?

 

thanks

Matt

Quote

I am a newbie. Just built my first kerne;/uboot for my RockPi S board.

That is a good head start. Welcome

 

4 hours ago, flatmax said:

* Are the kernel sources online ? For example :  linux-source-5.9.16-rockchip64.tar.xz

Unpatched sources are online, that is true. But what most likely want are the patched sources your kernel was made of. The build script always creates a source package at the same location as the other debs are stored: output/debs in your build script folder. Either install via dpkg or unpack via ar and tar

 

Quote

* If I want to add a devicetree overlay and driver code, what is the best way to do that ? Should I ammend the kernel ? Should I create an out of kernel package ?

Check this: https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-patches

7 hours ago, flatmax said:

If I want to add a devicetree overlay and driver code, what is the best way to do that ? Should I ammend the kernel ? Should I create an out of kernel package ?

And create a patch by using our tool - its easy and faster than going the manual way. 

 

./compile.sh CREATE_PATCHES="yes"

https://docs.armbian.com/Developer-Guide_Build-Options/

 

You can also build kernel on board but packing is not finished yet so you need to copy build artefact by hand. If that is not a problem ... armbian-config -> software -> kernel_sources ... they are identical to the image you are running and ready to fire "make".

Ok, thanks for the responses.

 

First of all, happy new year !!!

 

I see these different approaches you mention, however I still can't work out how to suit my development use cases.

 

Here are two use cases I have.

1. Say I want to include a software package. Perhaps the package has a debian directory, perhaps not. Do I need to check and update the package's debian directory ? Once done, how do I include that package in the armbian build ? For example here is the gtkiostream pacakge, which is useful to me and other audio people : https://github.com/flatmax/gtkiostream

 

2. Say I am building a new type of soundard, it requires out of tree kernel modules to be built. Is there a standard way to build out of tree kernelmodules and device trees ?

 

thanks

Matt

For standard package adds and customizations i would just add code to the Customize image script

 

For device tree and kernel modules you'll want to either use the Userpatches folders or just maintain your own branch of builder and have your patches there