Quote from Svartalf on September 2, 2011, 16:41
Quote from jamesh on September 2, 2011, 13:12
There is also the Armv6 instruction set on the Raspi, and the lack of memory which means only older versions of Android would be usable.
1.5, most likely. 2.0+ might be a problem.
Obviously Android would be targeted only for the model B versions with the 256MB RAM. That said, we have boards running Froyo and Gingerbread fine with 128-192MB RAM. And no, by running I don't mean booting to the home screen...
We are running some pretty big applications on it.
Only one driver would need to change to run on Android (and just a recompile I think) - the rest of the work is handled by Linux libraries which *I think* should work fine. The GPU blob is the same on Linux or Android - it's unrelated to the OS on the Arm.
You'd have to recompile everything to work with bionic. There's no glibc in the mix unless you're dragging your own with it, which is viewed as a no-no by Google.
I guess Jamesh meant that the other stuff (like audio) is handled by e.g. ALSA which is standard Linux, and supported by Android as well.
The problematic driver is the GPU userspace driver (not the GPU blob which is the firmware for the GPU), which will have to be ported to Android. In order to be useful, the OpenMAX codecs would have to be recompiled as well for use with Stagefright. I am pretty sure Broadcom did all this for their SoC, so it is really just a matter of intent on R-Pi.org's and Broadcom's side whether they want to release this or not.
What is also not yet clear to me whether this GPU will use the same system memory as the ARM core, so it could reserve say 64MB from the 256MB for itself to hold the firmware and runtime data, or will it have a dedicated memory above the 256MB.