Re: [FSO][M4] DOOM Running slow.

[Fox Mulder]

Could you please compile a version with these debug outputs?

I still can't play doom because i don't know the reason why it hangs at
the start screen. This would really help to solve the problem for me and
mayby some other debian users. :)

Fox Mulder wrote:
> I think the debug output would be very helpfull. When the doom menu
> appears the log says that the demo starts running but the screen never
> changes. It freezes at the menu where to select new game, options and so
> on. The behaviour is the same if i try it with framebuffer or xglamo and
> with or without rotate/resize.
> 
> Ciao,
>  Rainer
> 
> SCarlson wrote:
>> I haven't had a chance to install Debian and test Doom yet. I can say that I
>> had to use special patched binary of XGlamo for the scaling of the
>> touchscreen to work. If the game is running, but you can do anything (i.e.
>> demo is running) then I would assume that the touchscreen is not reporting
>> valid x,y coordinates. So I would say you may be subject to bug #1244 . Not
>> sure if someone has patched this for debian's xglamo package.
>>
>> Let me know if this helps? We can add some debug output and test on your
>> system if you'd like. (That way we could see for sure what reported x,y
>> values are being used.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO][M4] DOOM Running slow.

[Fox Mulder]

I think the debug output would be very helpfull. When the doom menu
appears the log says that the demo starts running but the screen never
changes. It freezes at the menu where to select new game, options and so
on. The behaviour is the same if i try it with framebuffer or xglamo and
with or without rotate/resize.

Ciao,
 Rainer

SCarlson wrote:
> I haven't had a chance to install Debian and test Doom yet. I can say that I
> had to use special patched binary of XGlamo for the scaling of the
> touchscreen to work. If the game is running, but you can do anything (i.e.
> demo is running) then I would assume that the touchscreen is not reporting
> valid x,y coordinates. So I would say you may be subject to bug #1244 . Not
> sure if someone has patched this for debian's xglamo package.
> 
> Let me know if this helps? We can add some debug output and test on your
> system if you'd like. (That way we could see for sure what reported x,y
> values are being used.
> 
> Scott
> 
> On Thu, Nov 13, 2008 at 1:25 PM, Fox Mulder (via Nabble) <
> [EMAIL PROTECTED]<[EMAIL PROTECTED]>
>> wrote:
> 
>> SCarlson wrote:
>>>  I've noticed extremely slow performance while running Doom on FSO M4. I
>>> tracked it down to the accelerometer code. (I turned off accel control in
>>> the opendoom.cfg file and that fixed the speed issue). The code basically
>>> opens /dev/event3 and reads from this. Should I be approaching the
>>> accelerometer interface differently?? It is running horribly slow, can
>>> anyone else confirm this?
>>>
>>> I've also noticed running from desktop on the phone is also very slow
>> with
>>> accel turned off as well. When running a similar startup script from ssh,
>> it
>>> runs full speed (accel still turned off).
>>>
>>> Is there anything obvious here regarding the way FSO operates that could
>>> cause this? I'd like to discover the cause and implement a solution
>> quickly.
>>> (Do I need to be on DBUS requesting the resources I need/want?)
>> Have you found the problem why doom isn't running on debian on fr?
>> I read people writing about it running and i still can't run doom. :(
>> I'm still stuck at the initial doom menu screen where nothing anymore
>> happens. I even installed xglamo and did resize and rotate the screen
>> but this didn't make any difference for the initial problem.
>>
>> Ciao,
>>  Rainer
>>
>> ___
>> Openmoko community mailing list
>> [EMAIL 
>> PROTECTED]
>> http://lists.openmoko.org/mailman/listinfo/community
>>
>>
>> --
>>  This email is a reply to your post @
>> http://n2.nabble.com/-FSO--M4--DOOM-Running-slow.-tp1493922p1494970.html
>> You can reply by email or by visting the link above.
>>
>>
> 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO][M4] DOOM Running slow.

[SCarlson]

I haven't had a chance to install Debian and test Doom yet. I can say that I
had to use special patched binary of XGlamo for the scaling of the
touchscreen to work. If the game is running, but you can do anything (i.e.
demo is running) then I would assume that the touchscreen is not reporting
valid x,y coordinates. So I would say you may be subject to bug #1244 . Not
sure if someone has patched this for debian's xglamo package.

Let me know if this helps? We can add some debug output and test on your
system if you'd like. (That way we could see for sure what reported x,y
values are being used.

Scott

On Thu, Nov 13, 2008 at 1:25 PM, Fox Mulder (via Nabble) <
[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> wrote:

> SCarlson wrote:
> >  I've noticed extremely slow performance while running Doom on FSO M4. I
> > tracked it down to the accelerometer code. (I turned off accel control in
>
> > the opendoom.cfg file and that fixed the speed issue). The code basically
>
> > opens /dev/event3 and reads from this. Should I be approaching the
> > accelerometer interface differently?? It is running horribly slow, can
> > anyone else confirm this?
> >
> > I've also noticed running from desktop on the phone is also very slow
> with
> > accel turned off as well. When running a similar startup script from ssh,
> it
> > runs full speed (accel still turned off).
> >
> > Is there anything obvious here regarding the way FSO operates that could
> > cause this? I'd like to discover the cause and implement a solution
> quickly.
> > (Do I need to be on DBUS requesting the resources I need/want?)
>
> Have you found the problem why doom isn't running on debian on fr?
> I read people writing about it running and i still can't run doom. :(
> I'm still stuck at the initial doom menu screen where nothing anymore
> happens. I even installed xglamo and did resize and rotate the screen
> but this didn't make any difference for the initial problem.
>
> Ciao,
>  Rainer
>
> ___
> Openmoko community mailing list
> [EMAIL 
> PROTECTED]
> http://lists.openmoko.org/mailman/listinfo/community
>
>
> --
>  This email is a reply to your post @
> http://n2.nabble.com/-FSO--M4--DOOM-Running-slow.-tp1493922p1494970.html
> You can reply by email or by visting the link above.
>
>

-- 
View this message in context: 
http://n2.nabble.com/-FSO--M4--DOOM-Running-slow.-tp1493922p1495167.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO][M4] DOOM Running slow.

[Fox Mulder]

SCarlson wrote:
>  I've noticed extremely slow performance while running Doom on FSO M4. I
> tracked it down to the accelerometer code. (I turned off accel control in
> the opendoom.cfg file and that fixed the speed issue). The code basically
> opens /dev/event3 and reads from this. Should I be approaching the
> accelerometer interface differently?? It is running horribly slow, can
> anyone else confirm this?
> 
> I've also noticed running from desktop on the phone is also very slow with
> accel turned off as well. When running a similar startup script from ssh, it
> runs full speed (accel still turned off).
> 
> Is there anything obvious here regarding the way FSO operates that could
> cause this? I'd like to discover the cause and implement a solution quickly.
> (Do I need to be on DBUS requesting the resources I need/want?)

Have you found the problem why doom isn't running on debian on fr?
I read people writing about it running and i still can't run doom. :(
I'm still stuck at the initial doom menu screen where nothing anymore
happens. I even installed xglamo and did resize and rotate the screen
but this didn't make any difference for the initial problem.

Ciao,
 Rainer

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO][M4] DOOM Running slow.

[Xavier Cremaschi]

> I noticed the same, but the solution from another thread worked here - 
> either execute or put into ~/.profile :
>  
> # fix doom accelerators
> echo 10 > /sys/devices/platform/lis302dl.1/threshold
> echo 10 > /sys/devices/platform/lis302dl.2/threshold
>  
> Stefan


Great tip ! That's why my Doom was so slow ( 
http://n2.nabble.com/forum/Permalink.jtp?root=1444789&post=1453633&page=y )

Thanks,
Xavier.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [FSO][M4] DOOM Running slow.

[Stefan Fröbe]

>  I've noticed extremely slow performance while running Doom on FSO M4. I
> tracked it down to the accelerometer code. (I turned off accel control in
> the opendoom.cfg file and that fixed the speed issue). The code basically
> opens /dev/event3 and reads from this. Should I be approaching the
> accelerometer interface differently?? It is running horribly slow, can
> anyone else confirm this?


I noticed the same, but the solution from another thread worked here -
either execute or put into ~/.profile :

# fix doom accelerators
echo 10 > /sys/devices/platform/lis302dl.1/threshold
echo 10 > /sys/devices/platform/lis302dl.2/threshold

Stefan
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community