* Rework packages install that they can be installed from repository instead of local compile. Handy for making releases.
* Don't build ATF if you don't build u-boot
* Config files moved to userpatches.
* Automatic move config-default.conf to userpatches folder
* Move Dockerfile to config/templates which is then copied to userpatches.
* Enable torrent dl by default
* Install docker if we want to build under Docker but its not installed
* Adjust Vagrant settings
Signed-off-by: Tian Yuanhao <tianyuanhao@aliyun.com>
Further I introduced the variable CRYPTROOT_PARAMETERS to have the ability to pass more options to the cryptsetup command.
I've test this on an Odroid HC2 (XU4) with default kernel configuration, full OS image, "next" branch and stretch as server:
- default without encryption
- encryption with user sepcific cryptsetup parameters
- encryption without user specific cryptsetup parameters
* helios4: next branch use u-boot 2018
use new u-boot based on upstream 2018
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* helios4: Tweak fancontrol configuration
Adjusted MINSTART and MINSTOP to suit both old and new fan.
Adjusted TEMP threshold so fan would stop or run in minimal speed when
the system idle.
Fixed wrong MINPWM value.
URL:https://wiki.kobol.io/pwm/#configuration-file
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: mvebu-next: use upstream helios4 dts
Helios4 device tree has been merged on upstream since 4.19.
Rework the patch to produce same device tree.
URL:https://patchwork.kernel.org/patch/10449393/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: Use boot-mvebu-next bootscript
Use boot-mvebu-next.cmd that make use of upstream's Generic Distro
Configuration.
Since loadaddr and fdt_addr varibales are no longer required, remove the
patch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: mvebu-next: Add workaround for SPI and SATA concurrent access issue
Concurrent access on SPI NOR and SATA drives can lead to unstable SATA.
Therefore as workaround, disable SATA controller when SPI flash access
is needed and make it as user configurable item in armbianEnv.txt
This workaround might applies to Clearfog too.
Refer to
Commit 59af84c07c ("Helios4: Add SPI bootloader install feature
(#1126)")
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Bootscripts: Fixed boot-mvebu-next.cmd
The environment setting (armbianEnv.txt) is loaded to RAM located on
${load_addr} but the env import use wrong address (${pxefile_addr_r}).
bootargs still expect ${boot_interface} which carried over from boot-
marvell.cmd. Upstream's distro configuration use ${devtype} instead.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* uboot: mvebu-next: only apply DT fixup script if it exists
* [ buildscript ] Add FORCE_BOOTSCRIPT_UPDATE option
If enabled bootscript will get updated during bsp upgrade.
* Helios4: Enable FORCE_BOOTSCRIPT_UPDATE by default in board config.
* Helios4: Added boot-marvell.cmd compability to u-boot 2018
Revert the changes to use boot-mvebu-next.cmd instead of boot-
marvell.cmd to prevent unbootable system due to incompatibility between
u-boot 2013.01 and boot-mvebu-next.cmd
This reverts commit 0f17ecb233babe ("Helios4: Use boot-mvebu-next
bootscript")
U-Boot 2018 will failed load dtb and script due to missing some
variables on boot-marvell.cmd. This will render the system unbootable.
Re-added and update loading-boot-scr.patch for backward compatibility
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
