All,
I have a driver that works in the same way as the Davinci driver (based
on it in fact)
And all seems to work fairly well with DirectFB 1.2.0 a few niggles to
be posted in different emails.
However,
If I upgrade to DirectFB 1.2.3 I have huge regression. It appears the
get_index function that is used to decide which of the 2 surfaces (in
Double buffered case) always returns 0.
This means just running df_andi gives the following output.
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2008 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2008-09-15 17:06) [ DEBUG ]
(*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0]
<8388608>...
(*) DirectFB/Input: STB225 Infra-red (1) 0.1 (directfb.org)
(*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0]
<8388608>...
(*) DirectFB/Input: STB225 Front Panel Keyboard (2) 0.1 (directfb.org)
(*) DirectFB/Graphics/STB22x: Acceleration enabled!
(*) DirectFB/Graphics/STB22x: Registering Primary screen
(*) DirectFB/Graphics/STB22x: Registering GFX layer 0 on Primary Screen
(*) DirectFB/Graphics/STB22x: Registering GFX layer 1 on Primary Screen
(*) DirectFB/Graphics/STB22x: Registering VIDEO layer 1 on Primary Screen
(*) DirectFB/Graphics/STB22x: Registering VIDEO layer 2 on Primary Screen
(*) DirectFB/Graphics: NXP Semiconductors STB22X 0.1 (NXP Semiconductors)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(!) NXP/STB22X/GFX: FBIOPAN_DISPLAY (fb0 - 0,751) failed!
--> Invalid argument
(*) Direct/Interface: Loaded 'FT2' implementation of 'IDirectFBFont'.
(!) NXP/STB22X/GFX: FBIOPAN_DISPLAY (fb0 - 0,751) failed!
--> Invalid argument
(!) DirectFB/Genefx: Could not lock destination!
--> Not supported!
(!) DirectFB/Genefx: Could not lock destination!
--> Not supported!
(!) DirectFB/Genefx: Could not lock destination!
--> Not supported!
(!) NXP/STB22X/GFX: FBIOPAN_DISPLAY (fb0 - 0,751) failed!
--> Invalid argument
Exiting DirectFB ...
(!) NXP/STB22X/GFX: FBIOPAN_DISPLAY (fb0 - 0,751) failed!
--> Invalid argument
This is obviously concerning. I was wondering if anyone was running 1.2.3 on a
Davinci board and could
verify that df_andi etc was working for them (must be double buffered FB etc).
I am pretty confident that something has changed inside the DirectFB core to
cause this issue
but I do not have a Davinci to check this.
Hope you can help and hope that if this is a DirectFB 1.2.3 issue that I can
help sort it for the 1.2.4 release
Daniel Laird
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
