I made the mistake of assuming that HAOS was a fully open source project, and set about developing a board support layer for a random TV box with an ARM CPU.
It was not mentioned anywhere that I looked, and it only became apparent after several weeks worth of work, that the generic ARM resources for this project are locked, and that an out-of-tree, generic ARM build would not be possible without the requisite Git permissions.
Can anyone explain to me why this might be so? I’ve contacted the people that I suspect may be able to clarify, and they simply won’t communicate.
Thanks, tom_I. Thanks also for placing this thread in the correct category.
Yes, it’s only until your generic_aarch64 board support layer build is partly up, and pulling (if I remember correctly, docker) resources from Github, that the issue comes about.
I can create a franken-green build, and get all the nabucasa green board associated docker resources, unimpeded. It’s only when your board identifies itself as a generic_aarch64 build, that the door to Git downloads snaps firmly shut.
I’ve gone through all the Git verification and authorization steps, but my out-of-tree, generic_aarch64 build needs something I don’t know how to, nor, I suspect, will I be able to give it.
p.s. I didn’t have this difficulty with the Git resources download for a generic_x86_64 build, though I only built that to run via emulation.
