1c9ef0872b
* Updated rockchip64-dev to u-boot v2019.10 and BL31 v1.30 (rk3399 boards) * Updated rk3399 to u-boot v2019.10 and BL31 v1.30 * Revert changes to renegade u-boot patches * Moved renegade u-boot patches into board dir * Added debug info for RockPro64 and switched sdmmc to fifo-mode * Disabled regulators in SPL for RockPro64 * Re-enabled sd vcc regulator in SPL for RockPro64 * Some device tree and config changes for OrangePi RK3399 * Fixed Rock Pi 4A's $BOOTCONFIG * Let some boards use mainline atf instead of the one in rkbin For example, roc-rk3399-pc can just boot the kernel using the mainline atf. * Add roc-rk3399-pc * Fixed reset in mainline ATF * Attached ATF version to v2.2 tag * WIP: sdmmc fifo-mode in SPL only * Renamed source config files * Reverted changes to rockchip64 sources config * Reverted patch moves * Add missing trust.ini patch to rk3399 u-boot * Reinstated tpl/spl patches in rk3399 family * Added $RKBIN_DIR prefix in rk3399 sources * Add demonstration of boards bootloader assignment in rk3399 |
||
|---|---|---|
| .github | ||
| config | ||
| lib | ||
| packages | ||
| patch | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| compile.sh | ||
| LICENSE | ||
| README.md | ||
| VERSION | ||
Armbian
Debian based Linux for ARM based single-board computers
How to build an image or a kernel?
Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).
- guest inside a VirtualBox or other virtualization software,
- guest managed by Vagrant. This uses Virtualbox (as above) but does so in an easily repeatable way,
- inside a Docker, systemd-nspawn or other container environment (example),
- running natively on a dedicated PC or a server (not recommended),
- 25GB disk space or more and 2GB RAM or more available for the VM, container or native OS,
- superuser rights (configured
sudoor root access).
Execution
apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh
Make sure that full path to the build script does not contain spaces.
You will be prompted with a selection menu for a build option, a board name, a kernel branch and an OS release. Please check the documentation for advanced options and additional customization.
Build process uses caching for the compilation and the debootstrap process, so consecutive runs with similar settings will be much faster.
How to report issues?
Please read this notice first before opening an issue.
How to contribute?
- Fork the project
- Make one or more well commented and clean commits to the repository.
- Perform a pull request in github's web interface.
If it is a new feature request, don't start the coding first. Remember to open an issue to discuss the new feature.
If you are struggling, check this detailed step by step guide on contributing.