Hi Ajaz, see below.
(Forwarding only to (dev) list)
See below for some comments.
Ajaz H wrote:
Dear Niels/All,
On analyzing, we found that ioctl() call in dfb_fbdev_pan() is
failed. This is the cause for realize_region() failure. The error
shown by ioctl() call is "invalid argument".
We just commented out the realize_region() call in
dfb_layer_region_flip_update(). (We don't know the impact of
commenting this call.) After this, our DirectFB test application is
working without any crash. But some flicker in graphics is observed.
I am quite surprised you see something at all..
If you have no region, you have no picture. So at some point later, it
does work, apparently..
Anyway, flicker is a bit vague as a description.
Do you mean that, if you don't change the picture (no flip, no blit)
that it flickers, or do you mean it flickers when you do quick
blitting/flipping (normally some sync issue, or wrong sync arguments) or
maybe you have a curtaining effect (mostly lost sync between back and
front buffer)?
Please help me to solve this flicker issue.
Is there any problem on commenting realize_region() call in
dfb_layer_region_flip_update() ?
In direcrfbrc we use "desktop-buffer-mode=backvideo".
On running test application i found a waring message as follows,
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(!!!) *** ONCE [USING OLD DRIVER! *** Use 'state->mod_hw' NOT
'modified'.] *** [gfxcard.c:869 in dfb_gfxcard_state_acquire()]
This is bad.
It means, like it says, that you are using an old driver.
Try to update it.
Thanks and Regards
Ajaz H
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
