mirror of
https://github.com/armbian/build
synced 2025-09-24 19:47:06 +07:00
efa87b1fb8
* Initial commit BPi R2: Currently working/not working: - u-boot: - builds with minor issues - patching and cleanup happens on 'https://github.com/chwe17/u-boot-mt' - next (https://github.com/frank-w/BPI-R2-4.14) - boots with minor issues - ETH doesn't work with nm - sata works - no wifi (needs driver from: https://github.com/frank-w/BPI-R2-4.4) - USB not working (xhci-mtk 1a1c0000.usb: fail to get vbus) needs investigation - appended device tree is needed due to u-boot doesn't work with fdt (kernelpacking needs adjustemts e.g. cat zImage dtb > zImage-dtb - dev (kernel.org master) - untested, needs adjustments in config (e.g. CONFIG_LOCALVERSION="") - since no defconfig is available config is based on frank-w 4.16 Kernel - Kernel builds without issues - manual packing of kernel and dtb similar to next The board boots, serial console is available but everything else must be expected as not working! - to do: - u-boot needs a cleanup - binary blobs needs investigation - eMMC is **not tested** and needs for sure adjustements! (don't try nand-sata-install!!!) - bootscript isn't tested (only manual boot over u-boot console at the moment) - both kernelconfigs aren't 'armbian standard' modules need to be adjusted Only use it when you know're familiar with u-boot commands! * Small fixes, add bootscript - add bootscript for patched u-boot (needs patching of u-boot, currently under investigation and not working properly) - revert cat zImage dtb > zImage-dtb (cause not working) - first cleanup of dev kernelconfig (remove CONFIG_LOCALVERSION="") * Minor fixup -kernelconfig for next was adjustet so that USB is recognized -firt bootscripts was written to boot with source command (doesn't work 100% reliable) -slightly adjustd boardconfig (e.g. bootscript) must still be considered as early wip! * small update (FDT works now) -working bootscript -adjusted boardconfig -earlyprintk activated in kernelconfig * First attempt to get ETH working -all interfaces are bridged together -performance sucks at the moment (not clear if it's related to insane network configuration or I miss something obvious... :P ) * Major update (see below for changes): - 4.14 kernel was dropped due to https://forum.armbian.com/topic/7296-bananapi-r2-csc-mt7623-as-new-boardfamily/?do=findComment&comment=55194 and following - boot.cmd was adjusted to 'clean' mainline behaviour - next build opition and its defaultconfg was removed (at the moment dev only) - rework of the network default configuration - default configuration will be over network.d **not** NetworkManager - per default all wired interfaces are bridged together to br0 (still wip) - old 'interfaces' configuration was removed - boardconfig is adjusted (no desktop until I've prove that HDMI works) - what works/ not works: - board boots up without manual u-boot hacking - SATA, USB3 (massstorage) is tested and works without issues - due to rework of network configuration this is still wip and must be considered as 'not working' * moved to network.d for configuration of wired network - renamed bsp packages - blacklist wired interfaces for NetworkManager - defined all wired interfaces as br0 in systemd/network - defined networkd als default renderer for bionic (not tested yet!) * The houskeeping commit: - BOARDFAMILY was renamed to mt7623 instead of mt7623n (including patchfolders etc.) - Network.d has no fully control over wired networkes (block NM from controll, start networkd on firstrun etc.) - Further cleanup kernelconfig - CPU temp is visible from userspace - missed switch driver loaded - cryptodrivers are there (not tested) - still a bunch of work * Add DMA mem alloc patch -under testing! * Add next option (4.17.y) stick dev to master (4.18-rc1 untested) * minor fixes: - solve kconfig issues between 4.17 and 4.18 - stick next branch to 4.18 - first attempts to bring up gmac2 (doesn't work currently) * switch to upstream u-boot - fix ext4 dependency in patch series - kernelpacking currently broken * add bootz & cmd_ext4 * resolved merge conflict * apply ugly u-boot patch, fix bootscript * remove unneeded stuff, apply forgotten stuff * update config for dev & clean up boardconf (remove xenial) * - drop dev and next, move into default. There is no intention to provide stock kernel - fixed board description, renamed to WIP, where it can be merged later - packing boot firmware to the u-boot package - docker dependencies (aufs will be added later. not essential) - attached to 4.19.y - loading armbianEnv.txt - UUID support (tested) - enabled ZRAM (tested) - enabled eMMC install (not quite working properly yet) - Bionic has some issues with systemd networking. * gov to ondemand (thermals are conservative anyway), remove unneeded kernelconfigs * Added AUFS, remove debug from kernel boot parameters, add ath10 mPCI support (which works) * add power-off-key and rtc * Added onboard wireless, but it's enabling is disabled by default. Too fragile. * Change to CSC target
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),
- 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.