FWIW (yes, you're talking about MeeGo openness, so I can state this!),

MeeGo.com platform does not in any way rely on closed source binaries.

The Nokia N900 hardware adaptation currently consists of:

* Bluetooth firmware, redistributable, kernel-independent, userland-independent firmware blob (this is fairly typical even on PC)
* WLAN firmware, redistributable, kernel-independent, userland-independent firmware blob (this is fairly typical even on PC)
* BME, redistributable binary blob
* TI OMAP3 SGX drivers, userland, redistributable binary blobs, matches with a kernel side driver that's fairly OK to forward port.
* Misc calibration tools for wlan, redistributable binary blobs, only really depending on a WLAN driver kernel interface
* PulseAudio algorithms for 3GPP compliance, redistributable binary blobs (you won't get good sound without this)
* Kernel, open source, no closed source modules
* Xorg driver for SGX, open source, but links to closed source SGX drivers (PVR2D interface, etc)
* Open source ofono/telephony driver and pulseaudio modules for speech communication with modem
* Misc scripts for startup and setup of N900 bits and pieces, open soure
* Camera firmware, open source (it's really just register poking). Basic camera features work without blobs.
* Battery measurement is done through kernel and open source metering
* Upcoming: blobs for accessing AGPS and almost Maemo5-quality camera usage.

For each of the closed source bits, we're actively exploring opportunities how to 1) build these in the future in case it's needed and 2) how to avoid situations where they cease to work.

As said above, rest of platform is OSS, including applications. You won't easily find sane hardware that doesn't in some way require closed blobs on ARM side. And don't say the Freerunner.

Given that the blobs exist and they are redistributable and usable, it's a better situation than not having them at all.