02-11-2016, 10:33 PM
(02-11-2016, 06:28 PM)taros Wrote:(02-11-2016, 03:45 PM)SkairkrohBule Wrote: The problem I think (and I could be wrong) is Allwinner. For good or ill, Pine64 have partnered with a company who are very closed in their approach to people using their products. If Allwinner don't want to reveal the details of their SoC, so be it. That isn't exactly Pine64's fault. But, as with the Raspberry Pi, they (Pine64) could make as much of the hardware as possible open.
But you do run into the issue of having access to everything then except the chip that drives the heart of the beast. Is that really more useful than having no access at all?
There is a datasheet and user manual for the A64 SoC, at http://wiki.pine64.org/index.php/Main_Page#Datasheet
There is also the A64 Linux kernel source code (version 3.10), at http://wiki.pine64.org/index.php/Pine_A6...re_Release
What Allwinner is not doing, is developing the Linux kernel source code in a way to be readily accepted in the official Linux kernel.
Such a task is difficult, but again, that is the case with most other SoC manufacturers.
There is however work initiated by Andre Przywara that can boot the latest Linux kernel version on the Pine64, at https://github.com/apritzel/pine64
Hey Taros
Ah, I had somehow overlooked that SoC datasheet/user manual info, cheers.
Part of what I meant was the situation seems similar with the Raspberry Pi. In theory the schematics are there to make your own, but Broadcom are not likely to sell you the chips needed to 'finish off' the device. If Allwinner are happy to sell their A64 chips to the general populous, so much the better. But I don't know if they are happy to do that...