jojo | 16 May 04:14 2013

can not display cursor when moving to DirectFB surface


It's normal to display cursor when i disable HW acceleration of DirecFB,

in the HW acceleration case, when i move the cursor to the DFB surface, it disappear.

It''s a bug ? Maybe cursor need to be HW accelerated also ? 

I use the GTK+(v2.24.15) top on DirectFB(v1.4.0).


- Jojo

directfb-users mailing list
mingyue | 10 May 14:21 2013

Why surface dump create a compressed file like xxx.pgm.gz

Dear Mailing List Administrators,

I want to make a screen shot, so I use surface->Dump to catch the screen. But I got a compressed file like xxx.pgm.gz which include a xx.ppm file.

I want to know how to make a xxx.ppm file directly instead of xxx.pgm.gz file. my directfb version is 1.4.11

Thank you

directfb-users mailing list
Liam Donaldson | 8 May 15:51 2013


Breakthrough Diet Exposed: Celebrity Doctor Uncovers The "Holy Grail of Weight Loss"

directfb-users mailing list
Mutyalu Gadam via LinkedIn | 31 Mar 12:59 2013

Invitation to connect on LinkedIn

Naveen Kumar,
Mutyalu Gadam wants to connect with you on LinkedIn.
Mutyalu Gadam
Software engineer at Tata Consultancy Services View Profile »
You are receiving Invitation emails. Unsubscribe.
This email was intended for Naveen Kumar B T (CPU Validation Engineer at Intel India). Learn why we included this. © 2013, LinkedIn Corporation. 2029 Stierlin Ct. Mountain View, CA 94043, USA
directfb-users mailing list
Anouar Abdelbari | 15 Mar 09:54 2013

XKB: Failed to compile keymap (XDirectFB)


I got this error message when I'm trying to run XDirectFB :

(EE) XKB: Couldn't open rules file /etc/X11/xkb/rules/Xfree86
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

NB : setxkbmap and xkbcomp are already installed. How can I solve that ??




directfb-users mailing list
Liam Donaldson | 11 Mar 13:13 2013

Re: message

directfb-users mailing list
Stanislav Kogan | 7 Mar 17:54 2013

DIrectFB 1.6 inteldrmfb no system found


I'm trying to make DirectFB work on my laptop in order to run qingy,
and I get a "No system found!" error from DirectFB.

fbset -i shows framebuffer name as "inteldrmfb". The hardware is
aLenovo x201 Tablet with a core i7 and the "core processor integrated
graphics controller", the kernel version is 3.7.1 the framebuffer
drivers are i915 and fbcon. Oh, and I'm running Gentoo, so this is a
custom built kernel.

I have experimented with various options in directfbrc to make sure
that the device is correctly defined but to no help. Can anybody help




Stanislav Kogan
eMail: s.kogan@...
Jon Pomrenke | 11 Feb 23:31 2013


I am trying to implement a double-buffering capable framebuffer using DirectFB 1.4-13. I'm doing something very similar to this example: . In short, the framebuffer allocates twice the memory of the display resolution, reports twice the resolution as the virtual resolution, and switches the active buffers through ioctl(/dev/fb0, FBIOPAN_DISPLAY).

My display layer is configured to use the extra framebuffer memory:
  DBCK(dfb->SetCooperativeLevel( dfb, DFSCL_FULLSCREEN ));
  DBCK( layer->SetCooperativeLevel( layer, DLSCL_EXCLUSIVE ));
  config.flags = DLCONF_BUFFERMODE;
  config.buffermode = DLBM_BACKVIDEO;
  DFBCK(layer->SetConfiguration(layer, &config));

My framebuffer reports properly as a double-buffered display:
  (*) FBDev/Mode: Switched to 240x320 (virtual 240x640)

Now here comes the complicated part. Because fbdev.c uses mmap to handle data transfer to the framebuffer, I have no events to trigger data transfer to the LCD within my framebuffer driver. The LCD was previously looping continuously on a FRAME_DONE IRQ so I'm trying to find a way to throttle the refresh.

If I work with a full screen window, FBIOPAN_DISPLAY is called and I can trigger the LCD refresh that way. If the window is not full screen, the double buffer is updated properly, but I don't get FBIOPAN_DISPLAY and, therefore, no LCD refresh.

The code in DirectFB-1.4.13/systems/fbdev/fbdev.c handling FBIOPAN_DISPLAY is here:
     switch (region->config.buffermode) {
          case DLBM_TRIPLE:
          case DLBM_BACKVIDEO:
               /* Check if simply swapping the buffers is possible... */
               if (!(flags & DSFLIP_BLIT) && !surface->rotation &&
                   (!update || (update->x1 == 0 &&
                                update->y1 == 0 &&
                                update->x2 == surface->config.size.w - 1 &&
                                update->y2 == surface->config.size.h - 1)))
                    D_INFO("%s()  -> Going to swap buffers...\n",__FUNCTION__ );
                         if (funcs->FlipRegion)
                              ret = funcs->FlipRegion( layer,

This leads me to believe that the only way to induce FBIOPAN_DISPLAY is to create all windows at the full screen resolution or explicitly call IDirectFBDisplayLayer::Flip(). Obviously creating full screen windows consumes unnecessary resources. Calling Flip explicitly, and when not actually necessary, causes the double-buffering system to go out of sync and display the inactive buffer. Am I missing something?

I'd like to configure DirectFB to pass some sort of external refresh event to the framebuffer system, such as a frame done, or pan display. It is looking more like the correct way is to implement the clock-based IRQ refresh and utilize double-buffering to prevent flicker...

Thanks for the help,
Jon Pomrenke
directfb-users mailing list
Lance Spaulding | 7 Feb 04:45 2013

Current version of WebKitDFB

I'm trying to use the latest versions of DirectFB, LiTE, and WebKitDFB
(webkitdfb-r124228 branch) from git but am unable to get input devices
to work in web pages.  With the current version, neither my touchscreen
nor a keyboard work in web pages (but both work using df_input). The
touchscreen was working correctly last time I updated (~4 months ago).

Here's the webkit configuration I'm using:

WebKit was configured with the following options:

Build configuration:
Enable debugging (slow)                                  : no
Compile with debug symbols (slow)                        : no
Enable debug features (slow)                             : no
Enable GCC build optimization                            : yes
Code coverage support                                    : no
Unicode backend                                          : icu
Font backend                                             : freetype
Networking backend                                       : curl
Optimized memory allocator                               : yes
JavaScript Engine                                        : jsc
Accelerated rendering backend                            : directfb

WebGL                                                    : no
Accelerated Compositing                                  : yes
Animation API                                            : no
Blob support                                             : yes
Color input support                                      : no
CSS3 Flexbox support                                     : no
CSS box-decoration-break support                         : yes
CSS Exclusions support                                   : yes
CSS Regions support                                      : yes
CSS Filters support                                      : no
CSS Compositing support                                  : yes
DeviceOrientation support                                : no
Directory upload                                         : no
DOM mutation observer support                            : no
Fast Mobile Scrolling                                    : no
Filters support                                          : yes
Fullscreen API support                                   : yes
Gamepad support                                          : no
Geolocation support                                      : no
HTML5 channel messaging support                          : no
HTML5 data transfer items support                        : no
HTML5 FileSystem API support                             : no
HTML5 iframe seamless attribute support                  : yes
HTML5 meter element support                              : yes
HTML5 microdata support                                  : no
HTML5 progress element support                           : yes
HTML5 track element support                              : no
HTML5 video element support                              : no
Icon database support                                    : no
JavaScript debugger/profiler support                     : yes
JIT compilation                                          : yes
Legacy WebKitBlobBuilder support                         : yes
Link prefetch support                                    : no
MathML support                                           : yes
Media source                                             : no
Media statistics                                         : no
Media stream support                                     : no
MHTML support                                            : yes
Opcode stats                                             : no
Page Visibility API support                              : no
Quota API support                                        : no
Register Protocol Handler support                        : no
RequestAnimationFrame support                            : yes
Scripted speech support                                  : no
Shadow DOM support                                       : yes
SharedWorkers support                                    : yes
Speech input support                                     : no
Spellcheck support                                       : yes
SQL client-side database storage support                 : yes
SVG fonts support                                        : yes
SVG support                                              : yes
Text Autosizing support                                  : no
Touch Icon Loading support                               : no
Web Audio support                                        : no
WebGL                                                    : no
Web Sockets support                                      : yes
Web Timing support                                       : no
Web Workers support                                      : yes
XSLT support                                             : yes

WebKit2 support:
WebKit2 support                                          : no
WebKit2 plugin process                                   : no

DirectFB configuration:
Use Cairo-DirectFB                                       : yes
FusionDale support                                       : no
FusionSound support                                      : no
Toolkit                                                  : lite

Any idea why this isn't working?

Also, on a separate topic, is there a way to enable a proxy server
in WebKitDFB?  I tried setting the shell variable http_proxy but
that didn't seem to work.

Thanks in advance,

What's wrong with this DirectFB Blit example?


I got the directfb image example, and I'm trying to blit an image, as stated here. So, this is my code:

#include <stdio.h> #include <unistd.h> #include <directfb.h> static IDirectFB *dfb = NULL; static IDirectFBSurface *primary = NULL; static int screen_width = 0; static int screen_height = 0; #define DFBCHECK(x...) \ { \ DFBResult err = x; \ \ if (err != DFB_OK) \ { \ fprintf( stderr, "%s <%d>:\n\t", __FILE__, __LINE__ ); \ DirectFBErrorFatal( #x, err ); \ } \ } /* reflection against y */ static int DFB_FIXED_POINT_ONE = 1; static const s32 mat_y[9] = { -DFB_FIXED_POINT_ONE, 0, 0, 0, DFB_FIXED_POINT_ONE, 0, 0, 0, DFB_FIXED_POINT_ONE }; static IDirectFBSurface *logo = NULL; int main(int argc, char **argv) { int i; DFBSurfaceDescription dsc; IDirectFBImageProvider *provider; DFBCHECK(DirectFBInit (&argc, &argv)); DFBCHECK(DirectFBCreate (&dfb)); DFBCHECK(dfb->SetCooperativeLevel (dfb, DFSCL_FULLSCREEN)); dsc.flags = DSDESC_CAPS; dsc.caps = DFBSurfaceCapabilities(DSCAPS_PRIMARY | DSCAPS_FLIPPING); DFBCHECK(dfb->CreateSurface( dfb, &dsc, &primary )); DFBCHECK(primary->GetSize (primary, &screen_width, &screen_height)); DFBCHECK(dfb->CreateImageProvider (dfb, "iconC.png", &provider)); DFBCHECK(provider->GetSurfaceDescription (provider, &dsc)); DFBCHECK(dfb->CreateSurface( dfb, &dsc, &logo )); DFBCHECK(provider->RenderTo (provider, logo, NULL)); provider->Release(provider); for (i = -dsc.width; i < screen_width; i++) { DFBCHECK(primary->SetRenderOptions(primary, DSRO_MATRIX)); DFBCHECK(primary->SetMatrix(primary, mat_y)); DFBCHECK(primary->FillRectangle (primary, 0, 0, screen_width, screen_height)); DFBCHECK(primary->Blit (primary, logo, NULL, i, (screen_height - dsc.height) / 2)); DFBCHECK(primary->Flip (primary, NULL, DSFLIP_WAITFORSYNC)); usleep(1000*10); // 10 microseconds } logo->Release(logo); primary->Release(primary); dfb->Release(dfb); return 23; }

I'm using DirectFB 1.4.11. The output of this program is a lot of:

`(!!!) *** WARNING [rotation not yet implemented] *** [gfxcard.c:2075 in dfb_gfxcard_blit()]` `(!!!) *** WARNING [rotation not yet implemented] *** [gfxcard.c:2075 in dfb_gfxcard_blit()]` `(!!!) *** WARNING [rotation not yet implemented] *** [gfxcard.c:2075 in dfb_gfxcard_blit()]`

Is this a problem of my DFB version? Is there a way to make this example run and blit the image?

(by the way, I didn't understand the DFB_FIXED_POINT_ONE variable, so I give any value to it to try)

Wellington B. de Carvalho

directfb-users mailing list
Anouar Abdelbari | 5 Feb 11:42 2013

Compiling XDirectFB

 I'm trying to compile XDirectFB for tests. After patching xorg-server i had
a problem when running automake --add-missing. I got the following message : 
"automake: cannot open < No such file or directory"
I can't understand what is happening and how can I solve that.


View this message in context:
Sent from the DirectFB Users mailing list archive at