Active Topics
-
Maemo repository (5)
to Community by dredlok706 - 1 day, 16 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 1 day, 18 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 12 hrs ago -
List of well performing apps on Leste (33)
to Maemo 7 / Leste by teroyk - 2 days, 20 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days ago - more...
| The Following User Says Thank You to w00t For This Useful Post: | ||
|
2011-10-06
, 09:43
|
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#43
|
Originally Posted by w00t
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.
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.
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.
 |
|
2011-10-06
, 09:44
|
|
Posts: 1,716 |
Thanked: 3,007 times |
Joined on Dec 2009
@ Warsaw, Poland
|
#44
|
Originally Posted by gerbick
http://www.raspberrypi.org/?p=201
When will we see device ports outside of x86 and the Nokia N900?
__________________
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
| The Following 6 Users Say Thank You to smoku For This Useful Post: | ||
 |
|
2011-10-06
, 09:48
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#45
|
Originally Posted by abill_uk
Talking about MeeGo here - but to be clear - just the core.
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.
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.
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
|
|
2011-10-06
, 09:53
|
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#46
|
Originally Posted by w00t
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.
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.
 |
|
2011-10-06
, 10:00
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#47
|
Originally Posted by abill_uk
Read this .
Not much of this actually makes sense to me because it seems all self inflicting.
Meego is common core you say but what "core" was it? was it a UI/GUI or was it an OS?.
<snip more nonsense>
Device drivers are either integrated directly with the kernel or added as modules loaded while the system is running.
In Hardware adaptation, they are, for the Hardware they are adapted for (why doesn't that make sense to you?)
The graphical user interface (or GUI) used by most Linux systems is built on top of an implementation of the X Window System.
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?
| The Following 4 Users Say Thank You to erendorn For This Useful Post: | ||
|
|
2011-10-06
, 10:10
|
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#48
|
Originally Posted by erendorn
Oh i realise a lot more than you think i realise
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?
.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).
|
|
2011-10-06
, 10:23
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#49
|
Originally Posted by abill_uk
I'm affraid none of this is my work, but I agree it's great
Keep up the great work
Originally Posted by abill_uk
I'll try.
and try to have the gentlemany qualities that Woot has because he is really good at explaining almost everything
 |
|
2011-10-06
, 19:19
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#50
|
Originally Posted by abill_uk
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.
But but how on earth can an OS be designed around CLOSED components???.
Do you really think that manufacturers will give you all source code to the devices they have put in there particular design? because without this there can not be an OS of any kind.
Or are you going to start from scratch with data sheets of every component?.
__________________
Nokia's slogan shouldn't be the pedo-palmgrabbing image with the slogan, "Connecting People"... It should be one hand open pleadingly with another hand giving the middle finger and the more apt slogan, "Potential Unrealized." --DR
Nokia's slogan shouldn't be the pedo-palmgrabbing image with the slogan, "Connecting People"... It should be one hand open pleadingly with another hand giving the middle finger and the more apt slogan, "Potential Unrealized." --DR
| The Following User Says Thank You to danramos For This Useful Post: | ||
 |
| Tags |
| déjà vu, for the fjords, just pining, meego is dead, not dead |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 08:25.
Furthermore: not all devices require closed components at all. Think commodity hardware.
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.