I think I will give some backstory which might be relevant. This product was born out of a need to migrate from Intel Edison in our high precision GPS equipment. We looked long and hard for Edison alternatives but there were none. They were either too big, or too expensive or did not have enough computing power. So we decided to build our own.
Disclosure: I am co-founder of Emlid, the company behind Neutis. Happy to answer any questions.
You must clarify that. You are on a technical forum and that simply is not acceptable. "Mainline" is 4.16-rc2, there is only one mainline, so you are saying it's shipping with an rc quality kernel that is still in active development?
Or do you mean it comes with an LTS? "Yocto and Debian". Debian does not use mainline kernel, in fact, no linux distro does, ever. What version of debian?
There is so much work done by the great linux-sunxi community, you can see the mainlining progress for H5 processor here: http://linux-sunxi.org/Linux_mainlining_effort
Sorry, it is the middle of the night here and I am not ready to confirm on the exact Debian version, but I believe that it has not been decided yet. You can contact us directly and we will get back to you with more info on this.
That's before you consider that they chose a SoC with considerable GPU/VPU capabilities that can only do HDMI or composite, the first you would never use in an embedded application where you have a fixed display, the latter you would never use, ever.
That's an odd statement. How are those two things related?
You can still run 32-bit binaries (including thumb-2) under 64-bit OS in 32-bit execution state -- as long as kernel is configured to use 4kB pages. So your usermode binaries don't need to be bigger.
Or you can take advantage of higher performing 64-bit mode.
(Unrelated, but my pet peeve, one thing a lot of people get wrong: 32-bit ARM (Aarch32 and most ARMv7) supports 1 TB of physical RAM and 64-bit IIRC 16 TB. Not sure where the idea 32-bit ARM could only support 4 GB comes from.)
Still Mali, though. Which I totally agree is crap. And no drivers for other display types.
Also in terms of support by the creators, if they're serious about the 10 year commitment then I'd say actually that is better than Raspberry Pi. Mindshare in the maker community isn't that important to someone doing serious embedded hardware development for production as long as the company behind it is solid. Which kinda sucks, I wish there was more incentive for chipmakers like Broadcom to be more open but...
I have great appreciation for the work Maxime Ripard et al. have been doing on mainline support for the various Allwinner chips, hence why I kicked in a few bucks for their kickstarter on reverse-engineering the Allwinner VPU:
https://www.kickstarter.com/projects/bootlin/allwinner-vpu-s...
But lets not kid ourselves, none of this was Allwinners doing and they could not give a fuck about mainline Linux.
Could you elaborate on this?
My experience has been that the BCM2710 (and the RPi 3 board, in general) has had better (and earlier) support in mainline than the Allwinner H5. A client of mine is shipping a product based on the RPi3 after evaluating both (including building their own H5 based board), because support for H5 on mainline was poor and lagging compared to the RPi3.
Hence why all extant Raspberry Pi 3s have a full GiB of RAM.