Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

A lot of them do, because they *have* to, under the conditions of their license. The Linux kernel is GPLv2, which means that if you distribute binaries, you must also distribute your source.

Furthermore: not all devices require closed components at all. Think commodity hardware.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

When will we see device ports outside of x86 and the Nokia N900? I would love to see this on a tablet.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

I really do appreciate your explanations because i am just not able to understand why the meego adaption has not made pace and what the problems were.

I am not trying to be unsulting in any way or form please realise this because it is purely lack of understanding why and what the meego.ce was actually meant to be.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

Talking about MeeGo here - but to be clear - just the core.

MeeGo was not encouraging to device hackers. It had draconian binary requirements which made it very difficult for tinkerers to get it running on devices they had lying around. One more public example of this was in the SSSE3 requirement for x86, effectively excluding any older AMD hardware, along with quite a bit of older Intel hardware.

Mer is a lot more relaxed about this: there's a stock i486 port which should run on just about anything, and on the ARM side, I believe there's an armv6 port, which also widens the door to a hell of a lot more devices (like the n810).

So that's one aspect of where MeeGo failed: running on everything.

As for CE, its aim is to be a community handset UI, day to day usable. I don't know what your complaints with it are (or were) so I can't really address them, and nor do I think they're quite on-topic in this thread, but I do encourage you to get an SD and try the 1.3 release. Things have come a long way, and we've generally got a lot of good feedback, although there's clear room for improvement, and we're going to work our asses off to make that happen. Pop onto #meego-arm on freenode if you need help trying it on an n900.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

I think your explanations are VERY encouraging and makes a few things a lot clearer and i thank you muchly for your time to answer me.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

Read this .
In Mer, device drivers are not integrated directly.
In Hardware adaptation, they are, for the Hardware they are adapted for (why doesn't that make sense to you?)

In Mer the GUI is not. (but the X Window server is implemented)

Mer is all the rest. The OS core. What is not device or UI dependent.

Maybe you just don't realize that there is a enormous lot of code between the GUI and the drivers?

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

Oh i realise a lot more than you think i realise ;).

I only wish this to come together and yes i very know the amount of work involved even in making a basic device driver and really maybe you no not realise the appreciation people will get from a polished UI that is more user friendly than the one we got at the moment from Nokia on the Maemo OS of the N900.

Keep up the great work and try to have the gentlemany qualities that Woot has because he is really good at explaining almost everything ;) (you do have them from time to time).

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

I'm affraid none of this is my work, but I agree it's great ;)

I'll try.

Re: MeeGo Reconstructed - a plan of action and direction for MeeGo
 

They, more or less, already do it for Android. If this works out well and adoption starts SOMEWHERE, I would expect that there's no reason not to expect similar support.