So there are a number of reasons for the break - greater processing capabilities of the OMAP3 platform (including support for hw acceleration of OpenGL, though this is something that might be possible for our OMAP2s with either some reverse engineering or some words in the right places, I am ever hopeful). This means that the new UI may be too much for our OMAP2 devices (though we should have a damn good try when it's finally released, closer to the device release date).

Next issue with supporting the OMAP2 platform is the addition of the hi def camera and always-connected HSPA. I imagine this will fundamentally change the applications that are provided and the way the device is used. I can understand Nokia not wanting to release a version for the OMAP2 devices which is hobbled and whose apps don't work as designed, etc.

We can still try to get a decent version working on the OMAP2, it won't be perfect (which is why Nokia aren't wanting to do it officially), but we should be able to get something pretty decent - either "Diablo on steroids" (current ui), or if we manage to make/steal a driver perhaps even the new UI. Many of the new apps probably won't work very well (crap camera, not always-on connectivity), but at the very least we should benefit from the back-end changes (library updates, messaging, etc.)

I should add here that Nokia are keen to support our efforts to do this, by the licensing changes that Peter mentioned, and by opening up components that we might need to get this working. They are behind this, but not for official releases.

So, let's get cracking and see if we can get a Fremantle (with Diablo-ui) running on the OMAP2 tablets and in the fullness of time, we can give the OpenGL version a try too!