Hey, do you know why amiberry seems to freak out when non-standard (defconfig) values are used? It's like it puts the flags in the wrong place and tries to read them as a part of a different command. Everything else seems to be doing fine, but amiberry is set to compile only as ARMv6 and nothing else. Is that a workaround or something? You mentioned that 3DO needs to be optimized for specific platforms, this may be the easiest way to do it is to allow it to be configured through buildroot instead of default set values so that it will optimize for the specific platform each time.
As of right now, I'm managing to compile everything but amiberry as AARCH64 little endian with FP_ARMV8 to speed things along. So far, it's compiling, but I still need to run some tests to see how much it sped-up. While ARM estimates, 15 - 30%, I may need to setup zram to make-up the RAM difference.
So, if you would like to run a test-build with this, a number of people have been looking for 64-bit builds and a few, like myself, were pointed here.
Maybe this is a post for another topic, but do you think it possible to toss together a test image of a batocera_rpi3-64_defconfig? I'm willing to help how I can, but it's not much.
