Automate BalenaOS build using

Hi, there are different ways to apply the customizations you mention, and using is not the right choice.

  1. Ideally, the ath10k firmware should be included in balenaOS by default. We would like to include as many networking modules and firmware by default, but the partition sizes are limiting this effort. We are working on mechanism that would allow to do this. Anyway, it’s always a good idea to request for the networking drivers to be included if they are used as we do include them when customers request them.

  2. Until the firmware is included in balenaOS, the beast approach would be to include the firmware in an application and install it into the rootfs at launch, then load the module. There are instructions to doing this in How to mount /lib/firmware RW - #4 by chrischabot.

  3. Another approach if you are doing a custom build would be to use barys to initialize the project, then copy a custom local.conf file to it, and then launch the build. Of course, custom builds cannot be used with balenaCloud, but it may be an option if you are using openBalena or balenaMachine.