* Bring Helios4 back as @heisath will keep maintaining it
* Status changes according to the meeting agenda
http://meeting.armbian.de/armbian.2024-02-10-15.01.html
* Revert ZeroPlus
* Add missing maitainer field
* Move qemu targets to csc
* change status for opir1lts+
This fixes the readability of colorized output of compile.sh when
running on a terminal with a light background. It uses the COLORFGBG
environment variable similarly to how the ip(8) command does.
Signed-off-by: Darsey Litzenberger <dlitz@dlitz.net>
- allows users to put .dts files bare in `userpatches/kernel/rk35xx-legacy/dt`
- important: everyone is still invited to send the DTs to https://github.com/armbian/linux-rockchip directly
- where yes, they'll have to patch the Makefile there as normal
- without incremental: true:
- we replace the DT Makefile based on *.dts at the DT directory after all patching/copying is done
- overlay target is added if overlays present
- with incremental: true:
- we parse the Makefile, parse the DTs being built, and only add .dts's we have added from 'dt' directory
- overlays target are not added; we assume smth else already added them
* aml-s9xx-box uses the u-boot shipped with the TV Box instead of installing
a new u-boot. Because of this, armbian-install will make the box unbootable
if it is run to install to emmc. This change prevents running
armbian-install on aml-s9xx-box boards
Changes to be committed:
modified: packages/bsp/common/usr/sbin/armbian-install
* prevent armbian-install from running on aml-s9xx-box take 2
Per suggestion of @viraniac remove armbian-install from the board bsp
via the board config file
Changes to be committed:
modified: config/boards/aml-s9xx-box.tvb
modified: packages/bsp/common/usr/sbin/armbian-install
The command added to check whether the directory is git or not was
having syntax error. Fixed the same. Also it seems adding safe-directory
with local doesn't really work which actually makes sense. hence
reverting to using global instead. Its still safer than before as
we are not adding * and are adding the actual path of the directory
* using the configured volume group name
* added LVM support
* ensuring /boot never on LVM volume, created hook to setup root device
* preparing root device via extension, not assuming any particular partition for root
* using tab spacing
* using global parameter to require a boot partition
* using boot require, moving cryptroot code to extension
* adds crypt image suffix
---------
Co-authored-by: rafael <rvalle@privaz.io>
