[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 5 June 2012 16:34, Gordon Henderson <gordon+lug@xxxxxxxxxx> wrote: > Android is built on Linux and in that sense it's just another Linux > distribution - although it's one that really knows how to handle the > hardware at the bit level - which under the Pi is going to be somewhat > challenging due to the closed nature of the GPU. The powers that be (ie. > google) have dictated minimum specs for ICS too - and the Pi just falls > short of that. 700MHz with about 190MB of free RAM (if using the GPU) is all > you get. > It would be marginal. Gingerbread might be a better fit. How do Google exercise these powers? Surely you can rip Android up how you want. I.e. just install their kernel and bionic or whatever their base is called nowadays. Or is it simply the case that the GPU is not supported and therefore, nothing works? > A down-side is that Android isn't easy to develop directly on (it's all > cross compiled) - so that would go against the aims of the RP Foundation - > which is to produce a stand alone PC which can be used for development - or > at least teaching progrmaming in an elementary sort of way - so Debian (and > others) are capable of being used directly to do devleopment, so that's what > the foundation are prefering. Cross compiling is fine on embedded. I'm thinking a cloud compilation service than a local compile. Nonetheless a native toolchain should be working and I'm now wondering... why isn't it on Android? Why can a gcc front end whatever be ported to Android on ARM? -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq