elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
xmn has quit [Ping timeout: 255 seconds]
norly has quit [Quit: Leaving.]
norly has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 248 seconds]
macros_2ndPC has joined #maemo-leste
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
udder has quit [Quit: die in fire]
Twig has joined #maemo-leste
udder has joined #maemo-leste
norayr has quit [Ping timeout: 252 seconds]
antranigv has quit [Ping timeout: 255 seconds]
fab_ has joined #maemo-leste
Pali has joined #maemo-leste
<freemangordon>
Wizzup: so, what is es2gears fps on you n900? I changed my card (which was already very fast) to sandisk extreme 128GB A2 card
<freemangordon>
no change, still 16fps
<Wizzup>
freemangordon: I will look later today
<Wizzup>
(family was visiting for the past few days, so was a bit occupied)
<freemangordon>
sure
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #maemo-leste
peterM_ has quit [Ping timeout: 252 seconds]
linmob has joined #maemo-leste
fab_ has quit [Quit: fab_]
akossh has joined #maemo-leste
antranigv has joined #maemo-leste
norayr has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
freemangordon: 34 fps for me with gears in background...otherwise 16 fps now
<arno11>
(es2gears)
<arno11>
is someone knowing a cmd to switch to GSM/2G mode ? i need that to test something with n900 calls
<freemangordon>
arno11: hmm, you didn't say "in background" before, no?
<arno11>
indeed but i was sure it was different before
<arno11>
(few months ago)
<freemangordon>
hmm
<arno11>
but maybe i'm wrong
<freemangordon>
maybe with older drivers
<freemangordon>
and omapfb
<arno11>
maybe
<arno11>
running as sudo es2gears shows omapdrm error
<arno11>
10fps
<freemangordon>
what ewrror?
<freemangordon>
*error
<arno11>
libEGL warning: MESA-LOADER: failed to open omapdrm: /usr/lib/dri/omapdrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
<freemangordon>
that's normal
<freemangordon>
ignore it
<arno11>
ok
<freemangordon>
maybe I shall implement dri3 in omap driver
fab_ has joined #maemo-leste
<freemangordon>
what is strange is that I see > 50% CPU usage by Xorg
<bencoh>
what would dri3 give?
<freemangordon>
no xorg protocol overhead
<bencoh>
oh
<arno11>
ok
<bencoh>
that sounds like a good thing considering Xorg takes a lot when active ... unless it just moves the cpu usage to some kernel task or to application process
<freemangordon>
I would expect PVR kernel thread to take lots of CPU
<freemangordon>
but it looks normal (~10% or similar)
<freemangordon>
could be that I am doing something stupid in the driver
<arno11>
xorg use more than 40 percent cpu for calls actually. crazy
<arno11>
more than 3 pulseaudio processes...
<freemangordon>
umm, xorg uses cpu during call?
<arno11>
yes a lot !
<freemangordon>
something is massively broken then
<arno11>
arround 39-45 percent
<arno11>
it is bad new and a good new lol
<arno11>
it means something is broken indeed but that means everything is ok with cpu usage during n900 calls
<arno11>
:)
<freemangordon>
I don;t see how is xorg involved in a call at all
<arno11>
i don't know
<arno11>
maybe pulseaudio
<arno11>
anyway probably 2 different issues
<freemangordon>
ok, removing compositing makes es2gears run with 47 fps
<arno11>
ok cool
<arno11>
what's the cmd ?
<arno11>
pls
<freemangordon>
ctrl->shift->N
<arno11>
ok thx
<arno11>
50 with overclock so quiet similar
<arno11>
now i understand why most retroarch cores only work full speed in fullscreen
<freemangordon>
50 is because it is kinda vsynced
<arno11>
oh yes makes sense
<arno11>
need to go. ttyl
arno11 has left #maemo-leste [#maemo-leste]
xmn has joined #maemo-leste
arno11 has joined #maemo-leste
<sicelo>
arno11: gsm/2G? forgot offhand, but look for 'technology' in the modem properties (or is it registration properties) ..