armbian-build/config/bootscripts
Gauthier Provost 14452e25e6 Helios4: Changes / fixes related to bootscript issue (#1169)
* 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 0f17ecb233 ("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>
2018-11-29 06:58:39 +01:00
..
boot-cubox.cmd Switching Cubox NEXT to mainline u-boot, adding a bunch of hummingboard/cubox related fixes on top of mainline source 2017-12-13 20:21:16 +01:00
boot-espressobin.cmd Make Espressobin boot script CRYPTOROOT compatible 2018-09-07 15:02:11 +02:00
boot-marvell.cmd Helios4: Add SPI bootloader install feature (#1126) 2018-10-08 13:44:36 +02:00
boot-meson64.cmd [Meson64] U-boot bump to 2018.11, move C2 to Meson64 U-boot 2018-11-20 23:49:53 -05:00
boot-mt7623.cmd Bananapi R2 (#1151) 2018-11-08 18:51:42 +01:00
boot-mvebu-next.cmd Helios4: Changes / fixes related to bootscript issue (#1169) 2018-11-29 06:58:39 +01:00
boot-odroid-c1.ini Enable Odroid C1 NEXT, 4.17.y ... usable as headless server. Known issues: stuck on reboot, need power cycle, no hdmi console, no DVFS. 2018-08-01 13:00:31 +02:00
boot-odroid-c2.ini Moving Odroid C2 default to 3.16.y 2018-06-22 10:57:55 +00:00
boot-odroid-xu4-default.ini [odroid xu4] Drop kernel 3.10.y, default -> offical 4.14.y, next = vanilla 4.19.y http://ix.io/1rcZ & dev = n/a 2018-11-07 11:11:51 +01:00
boot-pine64-default.cmd Added legacy kernel (3.10.107) targets for several A64 boards: Orangepi Win and Bananapi M64 were tested, the rest is untested: NanopiA64, Olinuxino A64 and Teres A64 2018-01-09 22:51:54 +01:00
boot-rockchip64.cmd [RK3399] DEV kernel bumped to 4.19.RC4, adjusted kernel config, set u-boot to v2018.09, fix serial console output, default boot console is now HDMI, tested on FA Nanopc T4; default kernel bumped to 4.4.160 and re-add patch which address some issues 2018-10-10 17:25:28 +02:00
boot-rockchip.cmd [Tinkerboard/MiQi] Fix eMMC boot problem on MiQi by reverting back to old u-boot, fix console that both are present, HDMI and serial, adjust boot script that we don't need hardcode DTB. U-boot variable is set to RK3288-tinker so adding symlink to RK3288-miniarm which represent the board in a legacy kernel. Added upstream patch, tested on MiQi and Tinkerboard S, default and dev, upgrades still need to be tested ... 2018-10-12 14:10:42 +02:00
boot-s5p6818.cmd [s5p6818] Adjust boot script to show HDMI console bootlog instead of serial. Adjust kernel configuration. @TonyMac32 CONFIG_BT_HCIUART_3WIRE is gone from config here as well. 2018-10-25 11:28:50 +02:00
boot-sun50i-next.cmd [ sunxi-dev ] Moving to 4.19.y Tested: H3, H5 (unstable?!), H6(no hdmi), R40 (no hdmi), A83T, A64, ... some wireless drivers were left. They need to be adjusted for 4.19.y 2018-11-13 11:50:40 +01:00
boot-sunxi.cmd [ sunxi ] fixed boot console output to match reality. In "both" mode you can have serial console login, but boot log goes to HDMI. In "serial" you (current "both" defaults) you get boot log to serial console, console login and blinking cursor on HDMI which is hard to spot. Lot's of people thinks board doesn't work ... 2018-11-10 21:16:39 +01:00
boot-udoo-neo.cmd udoo: Allow rootfstype specified in armbianEnv.txt to be used 2018-08-02 21:10:15 +10:00
boot-udoo.cmd udoo: Allow rootfstype specified in armbianEnv.txt to be used 2018-08-02 21:10:15 +10:00