Using extlinux.conf instead of the legacy set of boot.scr + text files.
Description
For some time now, I've been testing Armbian's startup mode and install on different platforms using the standard u-boot tools (extlinux.conf configuration files). To do this, minimal changes were added to the build system, which do not break the previous version and add the ability to smoothly add a new launch option and test it on different models. The ultimate goal is to smoothly switch to using the standard extlinux.conf configuration mechanism for models, where possible, and get rid of the old and cumbersome system of binary scripts and text files, simplifying and standardizing the startup process and configuring the primary startup parameters. For the first stage, you can create a DEV branch and check the general functionality of the new mode, so that it does not break the work of the current version and gradually add support for the new version to different models (at the choice of the maintainers).
Checklist
hide
Activity
Show:
balbes150 June 20, 2021 at 10:23 AM
How to use the new launch option. In the board description file, you need to add variables.
enables the use of the new mechanism :
SRC_EXTLINUX= " yes "
additional kernel startup command line variables that are needed for a specific model.
the name of the DTB file to be used for launching (to specify in the extlinux.conf settings file). If you do not specify this variable, the system will try to use the same DTB that is specified for this model in u-boot, i.e. it automatically determines the DTB depending on the u-boot being started.
High
For some time now, I've been testing Armbian's startup mode and install on different platforms using the standard u-boot tools (extlinux.conf configuration files). To do this, minimal changes were added to the build system, which do not break the previous version and add the ability to smoothly add a new launch option and test it on different models. The ultimate goal is to smoothly switch to using the standard extlinux.conf configuration mechanism for models, where possible, and get rid of the old and cumbersome system of binary scripts and text files, simplifying and standardizing the startup process and configuring the primary startup parameters. For the first stage, you can create a DEV branch and check the general functionality of the new mode, so that it does not break the work of the current version and gradually add support for the new version to different models (at the choice of the maintainers).