Jump to content


Photo

Developer documentation


  • Please log in to reply
5 replies to this topic

#1 kprince

kprince

    Newbie

  • Senior Members
  • Pip
  • 3 posts

Posted 11 January 2017 - 04:48 AM

Do you guys have any developer documentation? It seems like you could use help mainlining things, but it is hard to tell where to start

 

 



#2 Igor

Igor

    Administrator

  • Administrators
  • 2888 posts

Posted 11 January 2017 - 07:16 AM

I would propose to start with build environment - our tools.They are made to be used for end users to recompile kernel and change kernel options for example. Kernel come packed as deb, so handling is simple.

 

When you want to go further and edit the code and save changes to the patch, check CREATE_PATCHES options. Further, you can configure / use your own kernel config, patches and sources per kernel family. 

 

I am sure I forgot something and we could do more, but it's already usable.


Want to send me a private message? Stop and think again. If there’s no reason for it to be private, it should be public. Thank you!


#3 zador.blood.stained

zador.blood.stained

    Advanced Member

  • Moderators
  • 1609 posts

Posted 11 January 2017 - 11:23 AM

Do you guys have any developer documentation? It seems like you could use help mainlining things, but it is hard to tell where to start

Developer documentation for what kind of development?


Spoiler

#4 kprince

kprince

    Newbie

  • Senior Members
  • Pip
  • 3 posts

Posted 12 January 2017 - 04:17 AM

Developer documentation for what kind of development?

 

I am trying to understand both kernel and userland setup here -- and how it differs from mainline linux/debian/ubuntu/yocto/buildroot.



#5 Igor

Igor

    Administrator

  • Administrators
  • 2888 posts

Posted 12 January 2017 - 07:39 AM

We are trying to follow stock Debian as much as possible. Everything regarding boot goes to /boot -> u-boot script and script environment (armbianenv.txt), kernel, ramdisk, dtb to /dtb ... bootloader is different for each board, usually somewhere before one and only ext4 partition. Bootloader is installed / updated on "uboot".deb install ... Further we have some utilities to make life easier (changing screen resolution, eMMC installer, armbianmonitor, ...) and some fine tuning regarding performances, power saving, ...


Want to send me a private message? Stop and think again. If there’s no reason for it to be private, it should be public. Thank you!


#6 zador.blood.stained

zador.blood.stained

    Advanced Member

  • Moderators
  • 1609 posts

Posted 12 January 2017 - 12:16 PM

I am trying to understand both kernel and userland setup here -- and how it differs from mainline linux/debian/ubuntu/yocto/buildroot.

You can start by looking at the build script sources. Some tweaks and patches differ between board, kernel version and SoC family, and obviously the kernel versions will differ too (between different boards and between Debian/Ubuntu and Armbian images)

 

Most packages come from stock Debian and Ubuntu repositories, apart from kernel, u-boot, firmware and some multimedia related stuff.


Spoiler