* Enable additional motd tips showing some internal ads
33% probability of showing, just like for the armbian-config
* Update quotes and add expiration date support
* Change variable names
* Add support to download quotes from our server
* Fix curl parameters
* Keep only weekly update
* `meson64`: `6.0`: g12a and g12b pinmux patches from Radxa
* u-boot: `radxa-zero2`: Radxa's patches for the Zero2 on `v2022.10`
* u-boot: `radxa-zero2`: use `v2022.10` plus Radxa's patches
* `meson64` u-boot v2022.10: change `BOOT_TARGET_DEVICES` to try to boot USB, NVME and SCSI before SD, MMC, PXE, DHCP
* `radxa-zero`: include v2022.10 standard patches (eg: boot from USB first)
* `armbian-audio-config`: do nothing if aplay/amixer/alsactl missing; shfmt
* `armbian-hardware-optimization`: fix for `case` without `esac` introduced in #4417; `shfmt`
* AR-1301: Move Rock PI 4 C Plus to stable targets
* Add also minimal targets
AFAIK this will be the primary model
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
* `radxa-zero` & `radxa-zero2`: set `BOOT_FDT_FILE` explicitly; no real changes
* `radxa-zero2`: `6.0`/`edge`: update Radxa Zero 2 DTS patch with Radxa's latest
* `radxa-zero`: `6.0`/`edge`: update USB-C patch with "fix interrupt storm from fusb302"
* `radxa-zero`: use pure mainline v2022.10 u-boot with no patches
Without this, when mkimage fails (for example because the boot partition
is too small), install.log shows an error like:
mkimage: Write only 16310208/17794920 bytes, probably no space left on the device
But this does not terminate the build, so the compile script shows no
error and an image is generated, but it is unbootable.
This runs the script with -e, so when mkimage fails, the script fails,
which makes update-initramfs fail, which makes the build fail.
* Proposal to create a Community Supported config for Amlogic based
TV Boxes to pickup the work that was done previously by balbes150
but is no longer supported by him.
This also provides a place where development can occure within the
Armbian framework since others on the internet are producing builds
called Armbian that are not done from within the Armbian community.
Changes to be committed:
new file: config/boards/aml-s9xx-box.tvb
modified: config/sources/families/include/meson64_common.inc
modified: config/sources/families/meson-gxl.conf
new file: packages/bsp/aml-s9xx-box/boot/aml_autoscript
new file: packages/bsp/aml-s9xx-box/boot/emmc_autoscript
new file: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf
new file: packages/bsp/aml-s9xx-box/boot/s905_autoscript
new file: packages/bsp/aml-s9xx-box/boot/u-boot-readme.txt
new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905
new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x-s912
new file: packages/bsp/aml-s9xx-box/boot/u-boot-s905x2-s922
new file: packages/bsp/aml-s9xx-box/root/fstab.template
new file: packages/bsp/aml-s9xx-box/root/install-aml-s905-emmc.sh
new file: packages/bsp/aml-s9xx-box/root/install-aml.sh
* Merge sources
Co-authored-by: Igor <igor@armbian.com>
* Add initial RISCV support
* Add UEFI edge and current kernel configs
* Cleanup and adjust packages
* Those files were in wrong path
* Fix locations
* Ubuntu images built
* Remove Debian support as its too fragile
* Remove Pinta as it doesn't work under riscv
* Limitation is only for building images
* Remove obsolete switch
* Cleanup major arch config files
* Support for Docker building
* Move all legacy u-boot patches under one general legacy folder
* Move 32b Rockchip under 2022.04 and legacy for Miqi
Tested
* Move Rock 3A patch dir under legacy
* Move / merge meson64 patch folder into v2022.07
Merge 2022.04 (mainly Rockchip 32) into 2022.07, tested
* Remove not needed patch
* Add last kernel version to config
* Fix to flush volatile journald to prevent full /var/log at startup
* re-introduce directory / in non-rsync copy, and exclude journal* in this copy
Note: this may need some testing if someone doesn't use rsync
* Fix for non-rsync copy to Disk, since journal cannot be copied onto itself
* Backed up journal files are removed with vacuum, so no need to delete them separately
* Make room at boot by removing old logs, in addition to the removal later
every 15 minutes
* remove old archived journal files modified more than 1 day ago
* make sure volatile logging is used, since journald sometimes turns persistent at boot
remove unused commented lines in ramlog
* Fix check for configured journald volatile logging
* revert #3799, the rsync --delete
* Exclude /var/log/journal from install, and create empty /var/log/journal directory when it exists during install
Co-authored-by: dennis laptop <dennis@smartstatetechnolgy.nl>
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
Co-authored-by: Dennis <bijwaard@gmail.com>
Co-authored-by: dennis laptop <dennis@smartstatetechnolgy.nl>
