maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Mer should succeed in one device first, any one device (https://talk.maemo.org/showthread.php?t=44813)

u2maemo 2010-02-17 07:27

Mer should succeed in one device first, any one device
 
My biggest expectation for mobile device is some device running open source OS and have no limitation for OS upgraded and driver open.

The closest OS is Mer and it almost already succeed except ARM CPU manufacturer refuse to provide open source driver.

Why Mer wait for special manufacturer? There are many manufacturers for same level ARM CPU. Some hope to keep sth secret for high profit but this choice shouldn't be the only choice of all manufacturers.

After Mer have been success on one platform then more hardware manufacturer will choose to compatible with Mer otherwise they will lose a big market.

All user who have suffered from 18 month support then be abandoned and forced to buy new device should push independent mobile OS.

Mer should find the best way to success and not just wait for sth happen.

Mer perhaps doesn't have same goal with one ARM cpu manufacturer but independent OS shouldn't depend on any one. It should be the leader of this history trend.

Stskeeps 2010-02-17 07:50

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by u2maemo (Post 531601)
My biggest expectation for mobile device is some device running open source OS and have no limitation for OS upgraded and driver open.

The closest OS is Mer and it almost already succeed except ARM CPU manufacturer refuse to provide open source driver.

Why Mer wait for special manufacturer? There are many manufacturers for same level ARM CPU. Some hope to keep sth secret for high profit but this choice shouldn't be the only choice of all manufacturers.

After Mer have been success on one platform then more hardware manufacturer will choose to compatible with Mer otherwise they will lose a big market.

All user who have suffered from 18 month support then be abandoned and forced to buy new device should push independent mobile OS.

Mer should find the best way to success and not just wait for sth happen.

Mer perhaps doesn't have same goal with one ARM cpu manufacturer but independent OS shouldn't depend on any one. It should be the leader of this history trend.

Right, Look at MeeGo instead - they seem to want open source drivers too. But for most visions and ideas, MeeGo is the way to go.

I'll still be providing a Fremantle base for N8x0 under the Mer 'brand'.

AlMehdi 2010-02-17 09:29

Re: Mer should succeed in one device first, any one device
 
The problem with Megoo is that it's not Maemo. It is built with QT and RPM. I for instance want GTK+ and Debian. That is one of the goods with Mer.

I have not yet had any experiance of Mer but have looked more and more on it lately. (In swedish, Mer = More)

Btw.. How well do Mer run on N900, are the phone functions working?

And i do support u2meamos thoughts..

ruskie 2010-02-17 10:01

Re: Mer should succeed in one device first, any one device
 
What I'm hoping from Mer eventually would be something like what Openinkpot is trying to be to e-readers(a generic independant distro one can deploy on multiple e-readers). A generic independant distro one could deploy on a tablet device and have it work. MeeGo I don't really see it going that way.

Stskeeps 2010-02-17 10:06

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by ruskie (Post 531773)
What I'm hoping from Mer eventually would be something like what Openinkpot is trying to be to e-readers(a generic independant distro one can deploy on multiple e-readers). A generic independant distro one could deploy on a tablet device and have it work. MeeGo I don't really see it going that way.

I don't see any conflicts in MeeGo with that aim.

ruskie 2010-02-17 10:41

Re: Mer should succeed in one device first, any one device
 
It's governed by Intel and Nokia, and Linux Fundation is it's home. Frankly I don't really trust any of the three to be on the same page. But that's simply a personal reason.

Stskeeps 2010-02-17 10:49

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by ruskie (Post 531825)
It's governed by Intel and Nokia, and Linux Fundation is it's home. Frankly I don't really trust any of the three to be on the same page. But that's simply a personal reason.

And it's open source from the beginning. Fork, if needed.

AndyM 2010-02-20 12:03

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by ruskie (Post 531773)
What I'm hoping from Mer eventually would be something like what Openinkpot is trying to be to e-readers(a generic independant distro one can deploy on multiple e-readers). A generic independant distro one could deploy on a tablet device and have it work. MeeGo I don't really see it going that way.

From what I've read, Mer is dead; Meego, I don't know, too early to say. I'd certainly like something that prolongs the life of the n8x0, since the n900 is not the replacement I want for them.

FRZ 2010-02-20 20:25

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by AndyM (Post 538302)
From what I've read, Mer is dead; Meego, I don't know, too early to say. I'd certainly like something that prolongs the life of the n8x0, since the n900 is not the replacement I want for them.

Huh, so Mer is dead just like that? I guess Meego have a better chance being that it will have too strong companies behind it to make sure it goes well in a way ubuntu does. While Mer, although have community support was more of a one man project, which we can all understand is extremely hard. Well, I have no problems with it, as someone else mentioned, long as my N810 is supported until something better comes along.

christexaport 2010-02-20 21:07

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by AndyM (Post 538302)
From what I've read, Mer is dead; Meego, I don't know, too early to say.

Well that's pretty disrespectful, when the Mer project leader, Stskeeps, said above he's commited to Mer for N8xx devices.

And for the other guy, Maemo6 IS MeeGo, and will be the first instance of MeeGo for commercial use, though still retaining the .deb packaging at the moment.. It will be the foundation for MeeGo's Handheld UI, and the Netbook UI will ditch the old Moblin stuff, borrow elements of that UI, and the Qt UI toolkit for its construction, so that both have a familiar feel. The .rpm packaging issue really isn't one. Its just a file format at the end of the day. Just repackage the apps and keep moving.

christexaport 2010-02-20 21:08

Re: Mer should succeed in one device first, any one device
 
Mer has a better chance now, since more open stuff will be available. It'll mainly be for legacy devices.

AndyM 2010-02-22 20:24

Re: Mer should succeed in one device first, any one device
 
Quote:

Originally Posted by christexaport (Post 538898)
Well that's pretty disrespectful, when the Mer project leader, Stskeeps, said above he's commited to Mer for N8xx devices.

No disrespect was intended; I was basing my comments on what I read on what appears to be the Mer project blog.
Quote:

So, what will happen to Mer? We'll still be a subsection of the MeeGo community arguing for our positions, our ideas, our hopes and helping out where we can. Best way to shape the future is by participating.
That reads to me as though Mer as an alternative OS is over.

It then goes on to say
Quote:

Mer as a system will live on in Mer^2. A quick summary is it is a Debian 5.0 system building inside OBS with tricks making it feel like a Scratchbox for the packages, which makes most of the Fremantle platform build on it. It will work on X86 and on N8x0. Mer 0.17 will be imaged up soon and published - those who want to continue with that can. The goal is not to make a fully open source system - it will serve purpose to be a foundation on which to build a backport of Fremantle for N8x0. The hope is to be able to build most of closed things for Fremantle for N8x0 using this.
So, there may be a new project with a new name to effectively backport Fremantle to N8x0. Maybe it's semantics, but that all looks to me as though Mer itself is being wound up; some of the work already done may be built upon to give us something on the N8x0 at some point, which I'd love to see, but I'm not sure I'm holding my breath when that work is not going to be part of an ongoing project which would have been the case, if I understand what Mer was going to be.


All times are GMT. The time now is 21:00.

vBulletin® Version 3.8.8