AMD joins MeeGo

Posted Nov 15, 2010 15:20 UTC (Mon) by wingo (guest, #26929)
Parent article: AMD joins MeeGo

Meego just gets weirder and weirder.

AMD joins MeeGo

Posted Nov 15, 2010 16:23 UTC (Mon) by xxiao (guest, #9631) [Link] (12 responses)

it's for those who missed android boat?
wait for the day that I can do 'git clone && make'

AMD joins MeeGo

Posted Nov 15, 2010 19:15 UTC (Mon) by teknohog (guest, #70891) [Link] (9 responses)

"it's for those who missed android boat?"

Meego is the merger of Maemo and Moblin.

The first Maemo tablet shipped in 2005, and you can currently get a Maemo phone in the form of Nokia N900. It is a Debian-based distro using glibc, Xorg, Gtk, Qt etc., so you can compile and run anything you could on a typical Linux machine. For example, a friend of mine has used an N900 for seminar presentations using Openoffice and the TV output.

I do not know Meego in detail, but one can hope it stays as an open distribution. Maemo systems are computers in every sense of the word, unlike the gadgets that run Android or iOS.

AMD joins MeeGo

Posted Nov 15, 2010 19:55 UTC (Mon) by hitmark (guest, #34609) [Link] (1 responses)

while maemo was debian based (as was moblin 1.x), meego uses RPM and will transition away from gtk and onto qt as the main ui lib (the netbook and ivi builds from intel are still gtk based however). I think gtk will stay as part of the core for the time being tho, as anything else will create a very nasty transition.

and the opening talk of this meego conference was a repeated message of contributing to upstream. Unlike android, where we see google going back into the "shed" after a release to work on the next in private, meego will be worked on in the open. ever so often there will be a "freeze" and a set of builds, but between those there will be open development with continual interaction with the various upstream projects it makes use of.

However, it is unlikely that the builds will be what we see on the devices that gets to market. Linpro for instance have taken the netbook build and put their own interface and a virtual keyboard on top to make a tablet release. Said release still holds the netbook interface however, and a way to transition between the two (useful for say convertible netbooks).

And likewise, the phone ui (ux?) developed will probably not be what nokia will use on whatever meego product they releases. It will however be compatible with the meego ui so that developing for one can be used on the other (same libs and such).

AMD joins MeeGo

Posted Nov 21, 2010 6:08 UTC (Sun) by ferringb (subscriber, #20752) [Link]

IVI was partially qt in 1.0 (ivihome), and is near full qt in 1.1- navit and a packagekit UI are the only remaining gtk consumers at this point (and navit could use qt for painting easily enough).

AMD joins MeeGo

Posted Nov 15, 2010 20:03 UTC (Mon) by klbrun (subscriber, #45083) [Link]

And meego will not replace maemo on the N900, although you can configure the N900 to dual boot maemo and meego.

AMD joins MeeGo

Posted Nov 16, 2010 15:19 UTC (Tue) by xxiao (guest, #9631) [Link] (5 responses)

Android may not be as upstream as you like, but I can 'git clone && make' and begin to work quickly(adding a new platform).

Meego? I read the wiki a few times and still failed to build it, it's not straightforward to me at least.

Plus I wish Meego had chosen maemo's debian way instead of rpm/opensuse.

well, best luck, meego.

AMD joins MeeGo

Posted Nov 26, 2010 20:24 UTC (Fri) by jospoortvliet (guest, #33164) [Link] (4 responses)

Yeah it's nice that you can get the latest development android version and build it. Wait, no, it's not available, it's being developed in secred. !Fail.

MeeGo is developed in the open, entirely, AND they have a strong upstream-first policy (very much unlike Android). None of that matters to end users, but it does matter to Free Software. So I care and so do most reading LWN. Or they should.

Besides, if you want to try MeeGo, the stable release IS easy to get - just grab the binaries ;-)

AMD joins MeeGo

Posted Nov 26, 2010 20:33 UTC (Fri) by mjg59 (subscriber, #23239) [Link] (3 responses)

Really? Where's the upstream driver for the video hardware in any of the non-netbook Meego devices?

AMD joins MeeGo

Posted Nov 27, 2010 17:10 UTC (Sat) by jospoortvliet (guest, #33164) [Link] (2 responses)

Oh, so because the video drivers of mobile phones are pretty much never open you would say Android development is just as open as MeeGo. Sure, sure...

AMD joins MeeGo

Posted Nov 27, 2010 17:17 UTC (Sat) by mjg59 (subscriber, #23239) [Link] (1 responses)

No, I'm saying that "Upstream first" simply isn't true. "Upstream eventually", maybe, but not "Upstream first".

AMD joins MeeGo

Posted Nov 27, 2010 17:24 UTC (Sat) by jospoortvliet (guest, #33164) [Link]

The policy is indeed not a black-and-white upstream-first. The GOAL is upstream first, and code is not accepted into MeeGo if there is not at least a patch being reviewed by upstream. Again, it is not black and white, there is some wiggly room - as there should be. None the less, this policy is entirely different from the way Android does it's business.

AMD joins MeeGo

Posted Nov 19, 2010 19:36 UTC (Fri) by daniel (guest, #3181) [Link] (1 responses)

"it's for those who missed android boat?"

More like: it's for those who consider Java a dangerous obstacle to the future of mobile telephony.

AMD joins MeeGo

Posted Nov 26, 2010 20:25 UTC (Fri) by jospoortvliet (guest, #33164) [Link]

And those who like to work on the OS itself instead of hoping Google will do the right thing...