fafd26db7e
* Initial commit, cleanup of Rockchip default * clean up patches: - 100_DTS_Tinker_opp_LED was splitted into 3 patches - 100_DTS_opp for opp (adjusted to RKs 3 point description of opp Voltage) - 110_DTS_8723bs for the wifi driver -rename of 270-dts-tinker-bluetooth.patch -> 111_DTS_disable_AP6212_bluetooth.patch to keep wifi-chip stuff together - 120_DTS_led1_heartbeat - 190_dts_tinker_s_emmc was reworked and splitted - gpiomem node was removed and has its own patch (260_DTS_gpiomem_node) - i2c1 node was removed and has its own patch 270_DTS_activate_i2c1 - spi2 part was removed (defined in rk3288.dtsi), default CS will now be CS0 not 1 (no reason to change this) - vdd_log regulator is removed (the counterpart is missing anyway, and actually disabled in ASUS and Rockchips branch) --> own patch in case it gets activated - 120_workaround_tinker_board_reboot -> 130_workaround_tinker_board_reboot to get some free numbers... ;) * Renamed 190_DTS_tinker_s_emmc and splitted into DTS-Part and driver part (191_driver_mmc_adjustment) * Boots, Still no hdmi console * Rockchip Kernel config updates Thanks to @Ntemis for the config options, they fixed the framebuffer Still have runtime GPU errors related to power model |
||
|---|---|---|
| .github | ||
| config | ||
| lib | ||
| packages | ||
| patch | ||
| .dockerignore | ||
| .gitignore | ||
| compile.sh | ||
| config-docker.conf | ||
| config-vagrant.conf | ||
| Dockerfile | ||
| LICENSE | ||
| main.sh | ||
| README.md | ||
| Vagrantfile | ||
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. Please check the Armbian with Vagrant README for a quick start HOWTO,
- inside a Docker, systemd-nspawn or other container environment (example),
- running natively on a dedicated PC or a server (not recommended),
- 20GB 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.