Add board config for MXQ TV box

[domin144]

Description

This change introduces a config for MXQ TV box based on S805 chip. This revives the s805_autoscript file, which is being sought for by the factory boot loader, making it possible to boot from SD card.

How Has This Been Tested?

I built an image with:

./compile.sh build BOARD=aml-s805-mxq BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers internet multimedia' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm

I flashed an image on an SD card and booted the board. I was able to run xserver with display connected on integrated HDMI port and use mouse and keyboard connected to USB ports. Ethernet connection was working too.

Checklist:

Please delete options that are not relevant.

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

Notice

This is my first PR to this project, so any advice is appreciated. The board support and testing is not of high quality, but should not affect any other board and give good starting point for further work. Prior to these changes running armbian on the MXQ board requires non-trivial, manual adjustments to the image.

[igorpecovnik]

This is my first PR to this project, so any advice is appreciated.

Check if you can make use of existing boot scripts.

[domin144]

This is my first PR to this project, so any advice is appreciated.

Check if you can make use of existing boot scripts.

Odroid-c1 and onecloud are the closest boards, but neither script will work out of the box due to hard-coded dtb path. I could try to extend one of those scripts, but this is additional risk of breaking those boards (I have no access to those boards to test). I think it should better be done under a separate PR.

[domin144]

I tried unifying the s805 boot scripts. Most of the code could be common. The dtb file could be selected in armbianEnv.txt.

Yet, MXQ cannot use exactly same script, as it detects the bootdev variable by looking for s805_autoscript, while odroid-c1 does not use the variable at all and onecloud expects it to be provided externally.

bootdev is needed to read the armbianEnv.txt config, so the config cannot be used to switch between the three approaches.

[igorpecovnik]

Yet, MXQ cannot use exactly same script

OK, understand. Another thing. In the mean time, kernel v6.12 becomes the thing and next release target. Move it to that folder and test, then we merge this.

[domin144]

I can't see meson kernel updated on main. Do you refer to meson64 kernel? MXQ has a 32-bit processor.

[igorpecovnik]

I can't see meson kernel updated on main.

Yes, it hasn't been switched for all kernels. Having 6.12. on current is general wish / target. Feel free to do it - if it works for you, there are great chanches it will work for other devices. Anyway, none is one the officially supported list ...

https://github.com/armbian/build/blob/main/config/sources/families/include/meson_common.inc

[igorpecovnik]

Related: #7747

[domin144]

I can see that #7747 has a different set of patches and there is discussion on which kernel versions should be assigned to legacy, current and edge labels. These changes are possibly breaking. I am happy to follow and test the updated kernel later, but I really think we should not mix the things.

This change only introduces config, scripts and a single patch to device tree for the MXQ. It should not affect anything else. I don't want to mix it, with a kernel update and a new set of patches.