Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 1 day, 21 hrs ago - more...
 |
GeneralAntilles |
2008-02-27
, 13:16
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#21
|
Originally Posted by Benson
No, it's sort of a compromise right now. It's the GTK tooltip widget, same one as OMWeather uses. :\
Originally Posted by Benson
Quim didn't really give us an answer when it came up during thoughtfix's interview (thanks again Quim and Dan!). As far as I could read, it basically came down to, "They're closed, it's not gonna change anytime soon." No real reason was given, though.
 |
|
2008-02-27
, 13:52
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#22
|
Originally Posted by polossatik
Kinda difficult when there are undocumented hardware components. Where you have documented hardware, gnu purists already succeded in providing a better system (ubuntu, mandriva, and surely most other linux distro nowadays) than the commercial alternative (windows).
If GNU purists succeed in making a system that is better then the provided SW stack I'll bet a lot of people will be more then happy to use it
|
|
2008-02-27
, 13:56
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#23
|
Originally Posted by Johnx
Considering that it sucks power like there's no tomorrow and its performance is mediocre, I'd say they chose the cheapest wireless chipset
(ie, do we want GPL drivers for wireless or the best/cheapest wireless chipset we can get?)
(Hey, I don't blame them for that, I also bought some of the cheapest wireless adapters I could find, but they have open drivers and perform much better than the tablet's one)
|
|
2008-02-27
, 14:31
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#24
|
Originally Posted by TA-t3
Bluetooth driver is not closed, the source is in linux kernel. What is closed is the bluetooth firmware blob but that's pretty normal (see http://www.bluez.org/download.html for various firmwares) .
The components that I feel could and should be replaced are those three mentioned in an earlier posting: wi-fi, bluetooth and possibly the dsp code (at least the former two are always open source in linux kernels for other devices). There shouldn't be any reason for having closed wi-fi and BT drivers.
Audio could be replaced relatively easily, it is possible to access audio from ARM side and linux drivers exist or is possible to adapt them. Then DSP will simply sit unused. See linux port for Palm Tungsten T/T2 (OMAP 1510) for example, I think it uses same audio codec as 770.
wi-fi is a problem, see this mail for introduction
https://garage.maemo.org/pipermail/c...er/000001.html
basically there are two closed parts with open glue (=cx3110x.ko) between. To make it kernel-independent one needs to replace umac.ko module. As I understand it the firmware blob and the umac blob fit together so using some random open wi-fi stack with the firmware may be hard (just guessing).
__________________
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
|
|
2008-02-27
, 14:41
|
|
Posts: 139 |
Thanked: 24 times |
Joined on Sep 2005
|
#25
|
Originally Posted by luca
Do you have a reference for that? I thought cx3110 was pretty good in that regard.
Considering that it sucks power like there's no tomorrow...
| The Following User Says Thank You to jussik For This Useful Post: | ||
 |
|
2008-02-27
, 15:49
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#26
|
Originally Posted by polossatik
Man, that was beautiful. Thanks.
<snip>The fact that Nokia is trying to make a working business model based on (partial) GPL software is only to be applauded as it will only give more credibility to the opensource/gnu/.... "movement".
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
|
|
2008-02-27
, 19:11
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#27
|
Originally Posted by jussik
wgetting a big file uses 75% cpu (according to osso-statusbar-cpu), I suppose (but I may be wrong) that a sizeable part of it is due to the wifi transfer (on another arm system wget takes just 30%).
Do you have a reference for that? I thought cx3110 was pretty good in that regard.
I also suppose (but again, I might be wrong) that cpu consumption translates to power consumption.
Btw, I don't really care about wget performance, I noticed the problem because it's very taxing to stream video to the tablet, in part due to missing video optimization (even with the great work done with the mplayer port) but in part due to the wifi (lack of) performance/efficiency.
|
|
2008-02-27
, 20:44
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#28
|
Originally Posted by luca
I retried with the output redirected to /dev/null (writing to the flash takes its toll on the cpu) and "Osso mcspi" takes 41% cpu, while cx3110x takes 12%. So the cx3110 isn't completely to blame (though 12% isn't that low), but overall wifi takes more than 50% cpu.
wgetting a big file uses 75% cpu (according to osso-statusbar-cpu), I suppose (but I may be wrong) that a sizeable part of it is due to the wifi transfer (on another arm system wget takes just 30%).
 |
|
2008-02-27
, 22:00
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#29
|
I guess I'd be more concerned with power usage figures on the wifi itself? It uses CPU to drive it, of course, but I expect more of the power is directly consumed.
|
|
2008-02-28
, 05:46
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#30
|
Originally Posted by luca
Network transfers are CPU-expensive. This really says nothing at all about the chipset itself.
wgetting a big file uses 75% cpu (according to osso-statusbar-cpu), I suppose (but I may be wrong) that a sizeable part of it is due to the wifi transfer (on another arm system wget takes just 30%).