by summers » Sun Aug 16, 2020 11:17 am
$this->bbcode_second_pass_quote('moonman', 'b')oot scripts can be enabled on 2016 version as well, but I'm pretty sure it isn't enabled on either our or bodhi's U-Boot. I know I didn't enable it on ALARM U-Boot specifically, but I would have to check as it may have been enabled by default (unlikely).
1. AFAIK there are no patches from bodhi, besides the config. I know ALARM U-Boot does not use any bodhi's patches, if he added something himself to his U-Boot version. It's mostly mainline U-Boot + different config. NSA325 reboot bug was fixed with the help of our forum member.
I see no benefit in boot.scr for kirkwoods, as current system works well for most, but few corner cases. You are free to submit a pull request though, to make it happen, and if it's up to the standards I will accept it
https://github.com/archlinuxarm/PKGBUIL ... t-kirkwoodYes I can confirm that neither arch arm not bodhi kirkwood uboot have distro enabled, yes it was in the code then, but in those time fames most machines didn't use distro - can't remember when it took off, but was a year or two later.
I think the advantage I see, is just that kirkwood uboot configuration is currently different than most of the arch arm targets - and that makes maintenance a hassle - it means any question on kirkwood, need to remember to write code the uEnv.txt style.
If I've understood you correctly, only changes to uboot were adding (for NSA325):
u-boot/configs/nsa325_defcon
u-boot/include/configs/nsa325.h
u-boot/board/zyxel/*
If thats all, I'd probably look about both arch arm and bohdi code, and look at mainlining it. Yes its more hassle that way, but means its back in mainline again. Anyway really down to me getting the time - something thats in short supply.