- move Odroid C4 from legacy u-boot toward mainline
- get rid of dirty legacy u-boot code
- get rid of FAT boot partition
- briefly tested
- both kernels can operate with one standard boot script
- add upstream patch and adjust config
- fix console
- don't clock C4 too high by default
* Initial commit for kernel boot splash
* Add startup files to disable bootlog when system is up / down
* Update logo, remove deprecated one
* Introduce new u-boot variable bootlogo
* Adjust kernel config
* Make logo possible on Odroid XU4
- add legacy and current upstream patches
- delete xu4 environment since its not used
* Cleanup C2,C4, both tested, logo works on mainline,
- adding legacy upstream patches for c4
* Enable bootlogo by default on Odroid N2
* Enable logo on RK3399 desktop images
* Cleanup the rest of the environment files
* Add initrd hook that copy splash file to initrd.
* Missing logo bits for one boot scripts
* Enable boot logo on Pinebook A64
* Enable bootlogo on Teres
* Update config
when there are some reasons which board failed to boot, eg rootfs crashes.
/init will fail to panic().
panic()
{
local console rest IFS
if command -v chvt >/dev/null 2>&1; then
chvt 1
fi
echo "$@"
# Disallow console access
if [ -n "${panic?}" ]; then
echo "Rebooting automatically due to panic= boot argument"
sleep "${panic}"
reboot
exit # in case reboot fails, force kernel panic
fi
...
}
when panic is set, there is no chance to fail into a shell, to debug what happens.
and device just keep reboot.
remove panic from bootargs to make it possible for users to find out why their boards fail to boot.
Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
atomic_pool_size can be controlled by kernel cmdline,
coherent_pool=nn[KMG] [ARM,KNL]
then use this parameter to replace the patch.
Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
Setting load_addr to "0x44000000" (1088 MiB) is too high for boards with only 1GB of RAM, and causes boot failure. I tried some lower values, until I found "0x34000000" (832 MiB) to work. I made quite big steps, so we probably could find something slightly higher to work too, but I see no reason why we would need to do it.
Reference: https://forum.armbian.com/topic/8829-le-potato-c2-k2-419-lts-testing-thread/?do=findComment&comment=69850
- merging C2 and Meson family on the source level, C2 is still making own kernels, but sources, patches and configs are the same
- merged boot scripts for meson family. support for non existing legacy kernel was dropped from boot scripts, added UUID support, armbianEnv.txt
- Meson default remain on 4.14.y, NEXT moved to 4.17.y and DEV remains on master
- remove deprecated patches, remove wrong permissions in patches
- tested on C2, K2 and Le Potate. USB troubles are still present and common, while K2 and Lepotato might have boot/reboot troubles on 4.16+
- boards configuration cleanup
- moving K2 to the supported list. It's the same level of support as Le Potato
