Do you mean that the upstream progress of the Cubie4 has stopped? That's not a good sign -- although the 64 bit v8 architecture in the next rev is very exciting indeed! OCaml trunk has a native code generator for it, which works well enough in my qemu testing so far, so Mirage itself shouldn't be very difficult to get running.
-a > On 27 Aug 2015, at 07:01, Nick Betteridge <[email protected]> wrote: > > > Definitely recommend the Cubieboard2 or Cubietruck. > > I think that the sunxi development of cubieboard4 has dried up even though > it's marked to be included in the next release. The only issue I've found > with cubieboard2/3 - which is definitely the way to go - is that if you run > the boards with the pre-built images for a long time then the xapi stack > chews up all of the microsd memory by writing a lot to syslog. If you rebuild > the image with the xapi commented out of the build scripts then it works fine. > > Incidentally, next iteration of cubieboard - 5 - uses the allwinner h8 - > which has the A53's, is 64 bits running arm architecture v8. > > Nick > _______________________________________________ > MirageOS-devel mailing list > [email protected] > <mailto:[email protected]> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > <http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel>
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
