Update/RFC on MeeGo Compliance Specification

Mats Wichmann is the pointman for the MeeGo Compliance Specification, which aims to define what devices vendors and applications developers need to do for MeeGo applications to run across the portfolio of devices, and avoid fragmentation: At this point, comments are welcome (well, of course they're welcome at any time). The spec is still in PDF format which I know is not the ideal review medium as it makes it hard to submit patches. Remember, for issues that should be tracked, bug/feature filings are good, it's easy to miss nuances that are just on the list, or on IRC, etc. At the same time, there are now three work-in-progress Profile specs, which are directly on the Wiki. I don't know yet which ones of these will end up in the 1.2 specification - that's up to the workgroups to push - but if you have insights into filling these in, please share.

Overview of MeeGo ARM driver support situation

Martin Brook and Carsten Munk have been discussing the support of MeeGo's "hardfp" ABI on the support of various ARM system-on-a-chip (SoC)s: My first port was to GMA500 on the intel SW15 platform which was supported but for older kernels and other distributions. This target has now been sorted out by intel to the point that the EMGD driver is part of MeeGo now and is keeping step with MeeGo releases. Well done Intel.

Now on the ARM side there are a number of SOC vendors producing hardware which would be great targets for MeeGo if we had the right driver support.