Page 17 of 19 « First 71516 17 1819
Reply
Thread Tools
Benson's Avatar
Benson is offline Benson
2008-10-09 , 17:41
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#161
Originally Posted by ragnar View Post
Yes, changing resolutions is rather tricky. Take iPhone with 320x480 for instance. Changing the resolution for the next HW would then basically break the current 3rd party applications (or at least make them look bad) - especially since they still don't have resolution independence and are drawing their stuff using bitmaps.
Whereas with OS2008, 3rd-party apps would be fine, and Nokia stuff (and Skype) would be broken... from my experience with rotation, anyway.

(There is the obvious, if not great, option for the iPhone to jump to about 640x960, and use pixel-doubling for legacy support; we can't reasonably do that, because 1600x960 screens in <5" diagonal are not available or very useful.)
__________________
World's first inductively-charged N900!
 
eiffel's Avatar
eiffel is offline eiffel
2008-10-09 , 17:45
Posts: 600 | Thanked: 742 times | Joined on Sep 2008 @ England
#162
Originally Posted by johnkzin View Post
...the Tube does look interesting. Did I notice that it has 2 card slots?...
As far as I know, the 5800 has just one MicroSD hot-swappable slot (up to 16GB).

The confusion may have arisen because this slot is listed twice on Nokia's official spec sheet - once under "Memory" and once under "Connectors".

Roger.
 
Benson's Avatar
Benson is offline Benson
2008-10-09 , 17:55
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#163
Originally Posted by GeraldKo View Post
Qole,

Just enter the cpu-perform code in Xterm, close Xterm and keep going? Or is there more to this? Does it stay tweaked after you restart? And, heck, what does it mean to "peg" the processor? Thanks.
See http://en.wikipedia.org/wiki/Pegging; I don't think we're talking the cribbage definition...

Anyway, the ondemand regulator runs the clock up to some maximum with actual load; naturally, it lags a little, like an automatic transmission: step on the gas, start accelerating, lose acceleration while shifting, then really accelerate. The maximum is either 400/133 (with no DSP tasks) or 330/220 (with any DSP tasks).

Performance simply keeps it at the same maximum; 400 without DSP, but dropping to 330 whenever there's a DSP task.

If you know your DSP tasks are cool at 133 MHz rather than 220, you can actually disable frequency regulation to maintain 400 MHz all the time. AFAIK, this is fine for normal usage, where the DSP only handles mp3 decoding and BT HSP; it might not do so well with DSP-based A2DP, but I really don't know.... works just fine for DSP-based A2DP as well!
__________________
World's first inductively-charged N900!
Last edited by Benson; 2008-10-09 at 18:45. Reason: s/166/133/ (Thanks, lardman!)
 
Benson's Avatar
Benson is offline Benson
2008-10-09 , 18:05
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#164
Originally Posted by benny1967 View Post
Hoping/assuming that the future device will not be bigger than an N8x0 - how would a higher resolution help?
Device constraints != screen constraints; it's been suggested an N810-size platform could handle a 5" screen, and an N800-size definitely could.
Originally Posted by benny1967 View Post
You cant make fonts and gui elements any smaller. in reality you'd have the same space to work with, as long as the screen itself doesn't get bigger.
You can make them even crisper than they are, you can make fonts smaller (although you can right now, too; resolution's not limiting on this at present) and in fact you can make gui elements smaller, at the cost of having to use the stylus; this is useful for ported apps.

And there are too many things designed around pixel spacings (notably on the web) that would be usable fit to the N8x0 display's size, but demand more pixels.

I think on a 5" screen, going as far as 1280x800 is the threshold of usefulness; anything over that probably won't help. But we're still way short of that.
__________________
World's first inductively-charged N900!
 
benny1967's Avatar
benny1967 is offline benny1967
2008-10-09 , 18:11
Posts: 3,790 | Thanked: 5,718 times | Joined on Mar 2006 @ Vienna, Austria
#165
Originally Posted by GeneralAntilles View Post
Picture a display where you can't even see the pixels? Mmm. . . .
oh... i cannot see them on the n800. should i tell my doctor?
 
qole's Avatar
qole is offline qole
2008-10-09 , 18:16
Moderator | Posts: 7,109 | Thanked: 8,820 times | Joined on Oct 2007 @ Vancouver, BC, Canada
#166
Originally Posted by Benson View Post
If you know your DSP tasks are cool at 166 MHz rather than 220, you can actually disable frequency regulation to maintain 400 MHz all the time. AFAIK, this is fine for normal usage, where the DSP only handles mp3 decoding and BT HSP; it might not do so well with DSP-based A2DP, but I really don't know....
How do I do that? That could help too!
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
 
Benson's Avatar
Benson is offline Benson
2008-10-09 , 18:31
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#167
I believe using the null governor should work; however, mine currently seems to be latched at 400 regardless of what governor I use (even powersave!) so I can't test.

My experience, way back when this was first making the rounds after OS2008 was released, was that the performance kick was not significant, but I was thinking to try it now... maybe that's why?! (No, I know ondemand did work at one point. So I'm not sure what's up with this right now... I blame liqbase, though.)

EDIT: Well, going into liqbase, setting ondemand, and exiting leaves me with ondemand behavior, and then I can switch it via /sys/.../cpufreq/scaling_governor as expected.

Turns out null locks it at current speed, so you need to kick it into performance, then to null (naturally, you don't want any BT tasks running at the time, or you'll lock in 330); also turns out that BT encoding for HSP is not done as a DSP task, because it doesn't pull us down to 330, but playing mp3s in Media Player does.
__________________
World's first inductively-charged N900!
Last edited by Benson; 2008-10-09 at 18:42.
 
lardman is offline lardman
2008-10-09 , 18:42
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#168
If you know your DSP tasks are cool at 166 MHz rather than 220, you can actually disable frequency regulation to maintain 400 MHz all the time. AFAIK, this is fine for normal usage, where the DSP only handles mp3 decoding and BT HSP; it might not do so well with DSP-based A2DP, but I really don't know....
Well my dsp-sbc task works fine at 133MHz (i.e. ARM at 400MHz) so now you do know
 

The Following 2 Users Say Thank You to lardman For This Useful Post:
lardman is offline lardman
2008-10-09 , 18:44
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#169
I believe using the null governor should work; however, mine currently seems to be latched at 400 regardless of what governor I use (even powersave!) so I can't test.
This won't unhook the DSP-ARM link between the clocks, for that you need a patch to the DVFS subsystem (which I have somewhere if anyone wants it)
 
ragnar is offline ragnar
2008-10-09 , 18:53
Posts: 631 | Thanked: 1,123 times | Joined on Sep 2005 @ Helsinki
#170
The issue about increasing resolution that it's by no means 'free'. Drawing even 800x480 pixels on screen takes a lot more power and processing than say 320x480. Every pixel takes some operations, essentially, making the device smaller. Not to mention if the size is increased even more. I'd personally say that the 800x480 resolution is really good already
 
Reply
Page 17 of 19 « First 71516 17 1819

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 06:39.

Contact Us - Home - Archive - Top