Hi, I just want to know that why MMSFBLayer:etExclusiveAccess change my outputmode. My xml configuration is 1280@720, but after MMSFBLayer:etExclusiveAccess is called, what I can see is 640@480 mode, can anyone explain this? Thanks!
PS: I use directfb on /dev/fb0, disko 1.5

Hi adrian,

did you specify your resolution like this?

<dfbsettings>
<parameter name="xres" value="1280" />
<parameter name="yres" value="720" />
.
.
.
</dfbsettings>

What version of DirectFB are you using? And can you please
test your layer that you are using with the dfblayer tool,
if it supports the resolution of 1280x720.

Thanks,
Matthias

Hi Matthias,

my xml configuration:
<mmsrc version="1.1.0">
<global>
<parameter name="logfile" value="./logfile" />
<parameter name="inputmap" value="default" />
<parameter name="prefix" value="./" />
<parameter name="sysconfig" value="./" />
<parameter name="data" value="./" />
<parameter name="theme" value="default" />
<parameter name="firstplugin" value="1" />
<parameter name="shutdown" value="false"/>
<parameter name="shutdowncmd" value=""/>
</global>
<dbsettings type="config">
<parameter name="database" value="./db/mmsconfigdb" />
<!--parameter name="database" value="/home/share/xuss/02/db/configdb" /-->
<!--parameter name="database" value="/home/share/xuss/02/db/mmsconfigdb" /-->
</dbsettings>
<dbsettings type="data">
<parameter name="database" value="" />
</dbsettings>
<dfbsettings >
<parameter name="xres" value="1280" />
<parameter name="yres" value="720" />
<parameter name="outputtype" value="vesafb" />
<parameter name="videolayerid" value="0" />
<parameter name="videolayerpixelformat" value="ARGB1555" />
<parameter name="videolayeroptions" value="" />
<parameter name="videolayerbuffermode" value="BACKSYSTEM" />
<parameter name="graphicslayerid" value="0" />
<parameter name="graphicslayerpixelformat" value="ARGB1555" />
<parameter name="graphicslayeroptions" value="" />
<parameter name="graphicslayerbuffermode" value="BACKSYSTEM" />
<parameter name="vrect.x" value="0" />
<parameter name="vrect.y" value="0" />
<parameter name="vrect.w" value="1280" />
<parameter name="vrect.h" value="720" />
<parameter name="touchrect.x" value="0" />
<parameter name="touchrect.y" value="0" />
<parameter name="touchrect.w" value="0" />
<parameter name="touchrect.h" value="0" />
</dfbsettings>
</mmsrc>

And I use DirectFB-1.2.6.

I found out that IDirectFBDisplayLayer_SetCooperativeLevel->dfb_layer_create_context->dfb_layer_context_get_primary_region in DirectFB cause my problem, but why??

One more question, if I config with BACKSYSTEM buffermode will cause my board accel useless? My board uses stx7101 chip(set-top box). How to config my program to improve my gui performace? Now it runs very very slowly. Thanks!

OK, your configuration looks ok.

Can you please execute the following command and post the output:
dfblayer -m 1280x720 -f ARGB1555

Maybe your vesa framebuffer doesn't support the resolution and pixelformat.

Best regards,
Matthias

Hi Matthias,

Because DirectFB 1.2.6 hasn't dfblayer tools, so I tried DirectFB 1.0.0, here is the output bellow.

And one more question, if I config with BACKSYSTEM buffermode will cause my board accel useless? My board uses stx7101 chip(set-top box). How to config my program to improve my gui performace? Now it runs very very slowly. Thanks!

##################################################################
root@marco:/usr/local/tym_local/bin# dfblayer -m 1280x720 -f ARGB1555

=======================| DirectFB 1.0.0 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2007-12-07 13:08)
(*) Direct/Modules: suppress module 'keyboard'
(*) Direct/Modules: suppress module 'ps2mouse'
(!) Direct/Modules: Module 'libdirectfb_stblit_accel.so' did not register itself after loading! Trying default module constructor...
(!) DirectFB/gfxdrivers/dfb_stblit_accel: FB file descriptor = 3
(*) DirectFB/Graphics: ST Microelectronics STAPI Blit based graphic acceleration 0.1 (ST Microelectronics)
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................

FBDev Primary Layer

dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
dfb_stblit_accel_EngineSync()...............................
Width 1280
Height 720
Format ARGB1555
Buffermode BACKVIDEO

dfb_stblit_accel_EngineSync()...............................

Hi adrian,

if you're using BACKSYSTEM, you won't have hardware acceleration.
But you can use BACKVIDEO or FRONTONLY and the performance should
be better.

Regarding the resolution: The dfblayer output looks ok to me.
Can you try some of the directfb examples like df_dok to test if
it's running properly with the desired resolution? If not, you should
ask on the DirectFB mailing list, because then it's a problem with
DirectFB.

If it's running in 1280x720 resolution, we have to investigate further

Best regards,
Matthias