Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 10 hrs, 50 mins ago - more...
 |
|
2010-08-04
, 18:40
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#102
|
Originally Posted by Stskeeps
Can you explain in detail how these blobs are going to be maintained for the n900? For instance, many think the tearing problem (vsync ?) is caused by some graphics drivers that n900 owners don't have the source to. Is there a policy or procedure in place to address issues for these binary blobs? If not, and no one paid by Nokia is going to fix this code, I bet some of us would have no problem signing an NDA to help fix hacker versions of these things if need be.
In MeeGo, closed blobs are: battery management, 3d accelerator libraries, bluetooth and wifi firmware. Accessible by plugging in your IMEI and accepting the usual 'no warranties' license.
__________________
N9: Go white or go home
N9: Go white or go home
|
|
2010-08-04
, 18:41
|
|
Posts: 3 |
Thanked: 0 times |
Joined on Jul 2010
|
#103
|
Look at what is happening here... was this forums so fragmented and were there so many complaints before?
 |
|
2010-08-04
, 19:15
|
|
Posts: 266 |
Thanked: 89 times |
Joined on Jan 2010
@ Norway
|
#104
|
Dog is awake.
Bump.
Bump.
__________________
---
"Sex is not the answer. Sex is the question. Yes is the answer..."
---
"Sex is not the answer. Sex is the question. Yes is the answer..."
 |
|
2010-08-04
, 20:05
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#105
|
Originally Posted by daperl
If you're wondering about technicalities, we have a build target following the daily and weekly releases/major of MeeGo with the sources of the blobs. We're currently building so we get notified if the builds break as well as automatic publishing of the built blobs (coming this week, automatic images hopefully soon afterwards).
Can you explain in detail how these blobs are going to be maintained for the n900? For instance, many think the tearing problem (vsync ?) is caused by some graphics drivers that n900 owners don't have the source to. Is there a policy or procedure in place to address issues for these binary blobs? If not, and no one paid by Nokia is going to fix this code, I bet some of us would have no problem signing an NDA to help fix hacker versions of these things if need be.
I'm personally these days testing the SGX drivers for inclusion, let's see if they work properly first.
In case of staffing, see my earlier reply.
We have the N900 as a reference device for MeeGo, hence images has to work and pass QA. That implies a high standard and a commitment to keep things working.
We have a very minimal set of binaries so it should be possible to maintain them.
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
|
|
2010-08-04
, 20:11
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#106
|
Originally Posted by Stskeeps
Haha if we're going go with that then..
Some misinformation there - Nokia employees (incl kernel developers) plus subcontractors are paid to work on MeeGo for N900 hardware adaptation. By MeeGo I mean meego.com, not Maemo 6.
Technically we can already all run Meego on the N900. It just doesn't do anything useful that Maemo doesn't already do. =P
Originally Posted by inidrog
I believe the answer was don't expect the community release to come with Nokia services like Ovi Maps.
Question about 2) : Will Meego for N900 be a Phone or just a microcomputer. (sms, mms, mfe, and OVI store access .... all the things Nokia phones have?)
I haven't seen any answer to this, but I sure want to know what people believe (hoping is not that interesting).
Regards.
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
 |
|
2010-08-04
, 20:12
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#107
|
Originally Posted by daperl
It is caused by the entire stack, from the 3d libraries to ui toolkit to individual apps -- it's not only a matter of magically flipping a switch in the sgx driver (a switch that exists indeed, btw).
For instance, many think the tearing problem (vsync ?) is caused by some graphics drivers that n900 owners don't have the source to.
For example you can do tearfree video on a N900 with the current software set.
Last edited by javispedro; 2010-08-04 at 20:15. Reason: Adding "with the current software".
| The Following User Says Thank You to javispedro For This Useful Post: | ||
|
|
2010-08-04
, 21:39
|
|
Posts: 2,427 |
Thanked: 2,986 times |
Joined on Dec 2007
|
#108
|
Originally Posted by javispedro
Thanks for the info, but would you mind being more specific. Are you saying I can solve this inside something like an xorg.conf file? I'm trying to push the envelope, so I thought if I do things like disable double-buffering in GTK widgets, for example, I can avoid a performance hit. See what I mean? I'm a little lost. Please help this ignorant fool.
It is caused by the entire stack, from the 3d libraries to ui toolkit to individual apps -- it's not only a matter of magically flipping a switch in the sgx driver (a switch that exists indeed, btw).
For example you can do tearfree video on a N900 with the current software set.
__________________
N9: Go white or go home
N9: Go white or go home
 |
|
2010-08-05
, 08:30
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#109
|
Originally Posted by javispedro
It is caused by the entire stack, from the 3d libraries to ui toolkit to individual apps -- it's not only a matter of magically flipping a switch in the sgx driver (a switch that exists indeed, btw).
For example you can do tearfree video on a N900 with the current software set.
Originally Posted by daperl
More importantly, how can we believe you if we can't even prove it to ourselves, looking over the source code and tweaking it and supplying a patch back to the maintainer to QA and distribute the fix?
Thanks for the info, but would you mind being more specific. Are you saying I can solve this inside something like an xorg.conf file? I'm trying to push the envelope, so I thought if I do things like disable double-buffering in GTK widgets, for example, I can avoid a performance hit. See what I mean? I'm a little lost. Please help this ignorant fool.
 |
|
2010-08-05
, 08:33
|
|
Posts: 762 |
Thanked: 395 times |
Joined on Jan 2010
@ Helsinki
|
#110
|
Well the way I see it is, I'm really enjoying the N900 as it is. So I guess my N900 has very many years on it. It works for me, why should it stop doing that in the future? 
| The Following User Says Thank You to cjp For This Useful Post: | ||
PR1.3 has been said to be coming in no unclear terms by people inside nokia. I realize it's not an official announcement.. but typically companies don't look pleasing on it's employees putting egg on their face by speaking fallacies.
So I do expect a PR1.3 will come eventually.
I have 0 hope of anything beyond that, or that PR1.3 will bring anything significant beyond what we already have (excepting the Web API/qt mobility stuff if you care about that.)
The one link in the wiki about PR1.3 is not the only place I've seen it referenced, I'm just far too lazy to search through the history and find more.
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!