Reply
Thread Tools
Posts: 724 | Thanked: 1,255 times | Joined on Nov 2007 @ Cambridge, UK
#41
Originally Posted by abill_uk View Post
There you go it is still all about uncertainty and if's, why oh why can Nokia not do something right for us !?.
It's not uncertainty, this procedure was put in place for that exact purpose.

Also, considering how similar the drivers for the next device will be compared to the N900, I imagine we'll at least have another year or two of those drivers being supported.
 

The Following 2 Users Say Thank You to tswindell For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#42
Originally Posted by qgil View Post
* No matter how many UX changes vendors do, they need to provide the official MeeGo API if they want to call their product a MeeGo device.
* I bet the MeeGo build infrastructure (OBS) will minimize the rpm/deb hassle for developers. I expect the average user not to even bother about this.
* Closed hardware driver are problematic only when the owners don't provide updated versions for new releases. The MeeGo project is working hard to have those drivers owners on board.
This dont sound right coming from a huge company and my query would be obvious, WHY does Nokia use closed components? why cant they stick with open source instead of picking troubled components?.

It really does make me wonder that Nokia are not taking a backhander for the use of closed components to get a good deal out of them.

At the end of the day all and every argument is because of this.
 
Posts: 724 | Thanked: 1,255 times | Joined on Nov 2007 @ Cambridge, UK
#43
Originally Posted by abill_uk View Post
This dont sound right coming from a huge company and my query would be obvious, WHY does Nokia use closed components? why cant they stick with open source instead of picking troubled components?.

It really does make me wonder that Nokia are not taking a backhander for the use of closed components to get a good deal out of them.

At the end of the day all and every argument is because of this.
Because there are no open alternatives.
 

The Following 3 Users Say Thank You to tswindell For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#44
Originally Posted by qgil View Post
Nokia tries *a lot*. Ask hardware vendors.

There is a good discussion about this somewhere in this thread...

Basically, Nokia puts considerable effort pushing hardware vendors in that direction. Open source drivers play well with the Nokia chipset strategy and with Linux development. But of course these companies need to make business, so asking them to open their IPR without suggesting any alternative is not the best approach.

MeeGo, with Intel as initial founder (a company with good track offering open drivers), is one of the biggest and most concrete public actions Nokia could push in that direction.
Here is the answer to the problem but Intel dont manufacture every component but still no reason not to source them in the development stages.

Maybe Nokia should invest and buy into the closed component companies?.
 
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#45
I just dont understand why people are so greedy, surely a good open sourced component is going to sell much more than a closed?.

Things have really changed in the last few years thats for sure, we need to get back to basics in this world.
 
Posts: 724 | Thanked: 1,255 times | Joined on Nov 2007 @ Cambridge, UK
#46
In my experience it's mostly been laziness over greed, that and geniune IP concerns. It's business in the real world and unlikely to change any time soon.
 

The Following User Says Thank You to tswindell For This Useful Post:
Posts: 2,829 | Thanked: 1,459 times | Joined on Dec 2009 @ Finland
#47
@attila77
So basically We should not mix Meego and Nokia too much. See it like Google doing itīs andoird on itīs own pace and Nokia collaborating in Meego developement on itīs own. On the other hand we have devices that Nokia happens to do. Makes sense in business. So for example HTC and other companies who have ended up compiling their own version of newest android to SOME of their devices are doing it just for to market their devices and see how people react. They are not providing any certain information about next version or future. On the other side community can always make their own hacked* versions of android and install them to devices that are not anymore "officially" supported by Samsung/htc.

*and meego is probably in better stance (than android) when we are talking about compiling it to back to devices that are not anymore officially supported. You do not have to HACK so much.
 

The Following 6 Users Say Thank You to slender For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#48
Originally Posted by tswindell View Post
In my experience it's mostly been laziness over greed, that and geniune IP concerns. It's business in the real world and unlikely to change any time soon.
There is one REAL answer to all this, Nokia either buy up a manufacturer or start their own in whatever country offers the best solutions.

The most successful company will one that is dependent on nobody and can self produce everything from start to finish so really it is all down to investment.

Anyhow i still feel Meego will just become another Maemo because of closed source but as you said drivers dont change that much but they have to be open from the start at least.
 
Posts: 724 | Thanked: 1,255 times | Joined on Nov 2007 @ Cambridge, UK
#49
Originally Posted by slender View Post
@attila77
*and meego is probably in better stance (than android) when we are talking about compiling it to back to devices that are not anymore officially supported. You do not have to HACK so much.
Indeed, we've been able to flash whatever we like since the 770, this is something I hope will never change.
 

The Following 4 Users Say Thank You to tswindell For This Useful Post:
danramos's Avatar
Posts: 4,672 | Thanked: 5,455 times | Joined on Jul 2008 @ Springfield, MA, USA
#50
Originally Posted by slender View Post
*and meego is probably in better stance (than android) when we are talking about compiling it to back to devices that are not anymore officially supported. You do not have to HACK so much.
As far as closed apps go, maaaybe. Well, but we don't know that yet, do we? We don't know how these binary closed-minded source code blobs make their way into the compiling step yet until Nokia actually does one of these, documents it and lets us see it, right? And then, we don't know if the closed-source applications have a close relationship or dependency on those closed-source kernel drivers/modules.

If I understand things right, much like the closed-source nvidia drivers experience, if they made their device drivers/modules such that they need to be recompiled with every kernel, you'll ALWAYS depend on Nokia to grant you their blessing to run that new kernel on your device with the drivers to make them work until they tell you how they're linked/built/etc to work with the kernel build process.

Please correct me if I'm misunderstanding any of this.
 

The Following 2 Users Say Thank You to danramos For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 17:32.