The kernel was bumped to 5.15, so we patch the 5.15 wifi injection in.
Also, the defconfig file needs to be named _defconfig for copying it in and using it as a target.
With newer u-boot, we don't seem to need the patch for usbarmory mki
Patch from upstream for mkii u-boot requires newer u-boot as well, so bump it.
The usbarmory mk ii u-boot wasn't actually building for the usbarmory mkii, so we grab the patch from the git repo and enable usbarmory mk ii build support.
Add in patch for usbarmory mk1's microsd card detection in u-boot.
Update the github repo to point to the new repos instead of relying on github to redirect us.
Remove a removed dts file upstream for the usbarmory mkii.
Bump the u-boot used by both to 2021.07.
Since we do not have the debian keys in custom kernels, wireless-regdb doesn't properly load and without this you can't set the regdomain, so on boards that have a custom kernel, make sure to point to the upstream regulatory.db not the debian signed one.
See https://github.com/beagleboard/Latest-Images/issues/33 for more info
I dislike calling it current_dir since the current dir would be whatever we are in, when we are really talking about the base directory of the repository, so lets call it repo_dir.
Most of the arm boards don't have a realtime clock, and if the time is too far out of sync, networking doesn't work. systemd-timesyncd doesn't show the same issue so lets go ahead and install it in most of the images that weren't already doing so.
We don't use this anymore as we simply dpkg-reconfigure in the runonce scripts. So lets save a bit of time from doing the download and space of storing a package that never gets used.
We use growpart from the cloud-guest-utils package (actually from Canonical's repo on github), and this allows us to resize all of the filesystem without random dropping journals.
Tested on rpi0w, rpi4 (32bit and 64bit), pinebook, pinebook-pro, nanopi neoplus2, rpi2, odroid-c2. So I am thinking it's in a spot to make it available everywhere.
Also, somehow enabling ssh was dropped, likely due to misreading the purpose of "enable-ssh" service, which is a feature parity thing from raspbian where you could drop a "ssh" or "ssh.txt" file on /boot and it would enable ssh. We decided long ago however, to always eable ssh on the arm images.