From prageeth at msstyletech.co.jp Mon Mar 1 10:57:45 2010 From: prageeth at msstyletech.co.jp (Prageeth) Date: Mon, 1 Mar 2010 18:57:45 +0900 Subject: [directfb-users] Same PNG using DFB0.9.24 and DFB1.2.8 Message-ID: <002801cab925$a41c0a30$ec541e90$@co.jp> Hi All, We are in the process of upgrading a legacy DirectFB-0.9.24 system to DirectFB-1.2.8, the later being built using buildroot-2009.05. However, the PNG test image looks better on the legacy DFB than on the newer version! On using IDirectFBSurface::Dump(), the destination surface for RenderTo(), and the final window surface to which Blit() is done, are both found to be same using legacy and new DFB. However, the primary layer's surface seems to differ as in attached ppm files. Moreover, the legacy version dumps a pgm file also. The DFB configuration of both systems were found to be same as attached. There is no hardware acceleration involved. Frame buffer settings given by fbset were also found to be same. However, the older 2.6.14.2 kernel had to be retained so that various device drivers could be reused. Hope using an older kernel need not be an issue. Any suggestions or debugging tips would be of great help. Thanks, Prageeth -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: old_vs_new.zip Type: application/x-zip-compressed Size: 26293 bytes Desc: not available URL: From diegofons at apexar.com Thu Mar 4 13:32:25 2010 From: diegofons at apexar.com (Diego A. Fons) Date: Thu, 04 Mar 2010 10:32:25 -0200 Subject: [directfb-users] Help, overlapping drawing Message-ID: <4B8FA859.70501@apexar.com> Hi, What's the best way of drawing a moving shape over an image? Right now I have an IDirectFBWindow and an IDirectFBImageProvider is rendered in the window's surface, then I must draw a moving shape over this image. I tried getting a sub surface and drawing on it but I'm not able to clear it because the image is cleared too (in a previous post I was able to realise the problem). Also I tried to create a new surface for drawing the moving shape and then blit the surfaces, but the image is cleared and the result is a noisy image. So, can anyone help me on this issue? I hope you can understand my problem. Regards, Diego A. Fons. From mcmackerel at gmail.com Sat Mar 6 14:22:11 2010 From: mcmackerel at gmail.com (Asdf Ghjk) Date: Sat, 6 Mar 2010 14:22:11 +0100 Subject: [directfb-users] Questions about blitting, hardware acceleration and the Linux framebuffer device Message-ID: <1b0677171003060522w759a4cd6x3eb45e7fbfaf46cc@mail.gmail.com> This might be more related to blitting, hardware acceleration and the Linux framebuffer in general, but as the answers might be interesting to other people using DirectFB, I thought I'd ask anyway. 1. When your source data is in main memory, what does hardware-accelerated blitting do differently to achieve higher performance? If the operation is just to copy data from main memory to vram, then how could this ever be "accelerated"? 2. What makes the non-accelerated framebuffer so slow anyway? At least with a vesa framebuffer, just displaying the boot-up messages seem to take way more time than the actual initialization. Where is the bottleneck, and what's done differently in the accelerated case? 3. Is it possible to do a "real" page-flip on just the framebuffer device without hardware acceleration, or will this just be implemented by copying data from one region to another? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From enelson1000 at comcast.net Sun Mar 7 23:24:35 2010 From: enelson1000 at comcast.net (ed) Date: Sun, 07 Mar 2010 14:24:35 -0800 Subject: [directfb-users] mini2440 TSLIB - caught signal 11 when running dfbinfo Message-ID: <1268000675.3238.17.camel@ed-hp-laptop> I am trying to get DirectFB running on the mini2440. I am using openembedded to create my image. In the directfb_1.4.2.bb file I have entered the following in the extra OE configure section. EXTRA_OECONF = "\ --enable-debug \ --enable-trace \ --enable-extra-warnings \ --with-inputdrivers=tslib \ --enable-fbdev \ --enable-freetype=yes \ --enable-zlib \ --with-gfxdrivers=none \ --disable-sdl \ --disable-vnc \ --disable-x11 \ TSLIB_CFLAGS=\"-I${INSTALL_PATH}/include\" \ TSLIB_LIBS=\"-L${INSTALL_PATH}/lib\" \ " On the mini2440 I have exported the following variables. export TSLIB_TSDEVICE=/dev/input/touchscreen0 export TSLIB_CALIBFILE=/etc/pointercal export TSLIB_PLUGINDIR=/usr/lib/ts export TSLIB_CONFFILE=/etc/ts.conf I created a directfbrc file in /etc with the following lines. memcpy=libc debug debugmem debugshm trace I ran ts_calibrate to configure display before running dfbinfo. Verified that there is a symbolic link from event1 to touchscreen0. root at mini2440:/dev/input# ls -l crw-r----- 1 root root 13, 64 Mar 7 23:19 event0 crw-r----- 1 root root 13, 65 Mar 7 23:19 event1 crw-r----- 1 root root 13, 63 Mar 7 23:19 mice crw-r----- 1 root root 13, 32 Mar 7 23:19 mouse0 lrwxrwxrwx 1 root root 6 Mar 7 23:19 touchscreen0 -> event1 But when I run dfbinfo the program crashes right after probing tslib input driver. Below is the output. ANY IDEAS ?????? ============================================================ root at mini2440:/# dfbinfo (-) [ NO NAME 0.000] ( 2182) DirectFB/Config: Unable to open config file `/home/root/.directfbrc'! (-) [ NO NAME 0.002] ( 2182) DirectFB/Config: Unable to open config file `/etc/directfbrc.dfbinfo'! (-) [ NO NAME 0.003] ( 2182) DirectFB/Config: Unable to open config file `/home/root/.directfbrc.dfbinfo'! (-) [ NO NAME 0.004] ( 2182) Direct/Main: direct_initialize() called... (-) [ NO NAME 0.004] ( 2182) Direct/Thread: direct_thread_set_name( 'Main Thread' ) (-) [ NO NAME 0.005] ( 2182) Direct/Thread: -> attaching unknown thread 2182 (-) [ NO NAME 0.005] ( 2182) Direct/Mem: + 120 bytes [thread.c:369 in direct_thread_set_name()] (-) [ NO NAME 0.006] ( 2182) Direct/Mem: + 12 bytes [thread.c:386 in direct_thread_set_name()] -> 0x13d48 " Main Thread" (-) [Main Thread 0.007] ( 2182) Direct/Main: ...initializing now. (-) [Main Thread 0.008] ( 2182) Direct/Signals: Initializing... ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.2 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ (c) 2001-2009 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH ---------------------------------------------------------------- (-) [Main Thread 0.030] ( 2182) DirectFB/Core: dfb_core_create... (-) [Main Thread 0.030] ( 2182) Direct/Main: direct_initialize() called... (-) [Main Thread 0.031] ( 2182) Direct/Main: ...2 references now. (*) DirectFB/Core: Single Application Core. (2010-03-07 21:23) [ DEBUG ][ TRACE ] (-) [Main Thread 0.033] ( 2182) Direct/Modules: direct_modules_explore_directory( 'systems' ) (-) [Main Thread 0.044] ( 2182) Direct/Mem: + 44 bytes [modules.c:229 in direct_modules_explore_directory()] (-) [Main Thread 0.045] ( 2182) Direct/Mem: + 21 bytes [modules.c:237 in direct_modules_explore_directory()] -> 0x13de0 " libdirectfb_fbdev.so" (-) [Main Thread 0.045] ( 2182) Direct/Modules: Loading '/usr/lib/directfb-1.4-0/systems/libdirectfb_fbdev.so'... (-) [Main Thread 0.077] ( 2182) Direct/Modules: Registering 'fbdev' ('systems')... (-) [Main Thread 0.077] ( 2182) Direct/Mem: + 6 bytes [modules.c:134 in direct_modules_register()] -> 0x157f0 " fbdev" (-) [Main Thread 0.078] ( 2182) Direct/Modules: ...registered. (-) [Main Thread 0.078] ( 2182) Direct/Mem: + 44 bytes [modules.c:229 in direct_modules_explore_directory()] (-) [Main Thread 0.079] ( 2182) Direct/Mem: + 22 bytes [modules.c:237 in direct_modules_explore_directory()] -> 0x15c98 " libdirectfb_devmem.so" (-) [Main Thread 0.079] ( 2182) Direct/Modules: Loading '/usr/lib/directfb-1.4-0/systems/libdirectfb_devmem.so'... (-) [Main Thread 0.090] ( 2182) Direct/Modules: Registering 'devmem' ('systems')... (-) [Main Thread 0.090] ( 2182) Direct/Mem: + 7 bytes [modules.c:134 in direct_modules_register()] -> 0x160c0 " devmem" (-) [Main Thread 0.091] ( 2182) Direct/Modules: ...registered. (-) [Main Thread 0.093] ( 2182) Direct/Mem: + 44 bytes [core.c:297 in dfb_core_create()] (-) [Main Thread 0.094] ( 2182) Direct/Mem: + 24 bytes [thread.c:113 in direct_thread_add_init_handler()] (*) Direct/Memcpy: Forced to use libc memcpy() (-) [Main Thread 0.095] ( 2182) Direct/Main: direct_initialize() called... (-) [Main Thread 0.096] ( 2182) Direct/Main: ...3 references now. (-) [Main Thread 0.096] ( 2182) Direct/Mem: + 532 bytes [fusion.c:2468 in fusion_enter()] (-) [Main Thread 0.097] ( 2182) Direct/Mem: + 2520 bytes [fusion.c:2474 in fusion_enter()] (-) [Main Thread 0.097] ( 2182) Direct/Mem: + 128 bytes [fake.c:54 in fusion_shm_pool_create()] (-) [Main Thread 0.098] ( 2182) Direct/Signals: Adding handler 0x40079845 for signal -1 with context 0x16010... (-) [Main Thread 0.098] ( 2182) Direct/Mem: + 28 bytes [signals.c:141 in direct_signal_handler_add()] (-) [Main Thread 0.099] ( 2182) DirectFB/Core: Initializing... (-) [Main Thread 0.100] ( 2182) Direct/Mem: + 128 bytes [fake.c:54 in fusion_shm_pool_create()] (-) [Main Thread 0.100] ( 2182) Direct/Mem: + 120 bytes [core.c:1046 in dfb_core_arena_initialize()] (-) [Main Thread 0.101] ( 2182) Direct/Mem: + 128 bytes [fake.c:54 in fusion_shm_pool_create()] (-) [Main Thread 0.116] ( 2182) Direct/Mem: + 136 bytes [object.c:179 in fusion_object_pool_create()] (-) [Main Thread 0.117] ( 2182) Direct/Mem: + 19 bytes [object.c:190 in fusion_object_pool_create()] -> 0x152a0 " Layer Context Pool" (-) [Main Thread 0.118] ( 2182) Direct/Mem: + 136 bytes [object.c:179 in fusion_object_pool_create()] (-) [Main Thread 0.119] ( 2182) Direct/Mem: + 18 bytes [object.c:190 in fusion_object_pool_create()] -> 0x15418 " Layer Region Pool" (-) [Main Thread 0.444] ( 2182) Direct/Mem: + 136 bytes [object.c:179 in fusion_object_pool_create()] (-) [Main Thread 0.445] ( 2182) Direct/Mem: + 13 bytes [object.c:190 in fusion_object_pool_create()] -> 0x15430 " Palette Pool" (-) [Main Thread 0.446] ( 2182) Direct/Mem: + 136 bytes [object.c:179 in fusion_object_pool_create()] (-) [Main Thread 0.446] ( 2182) Direct/Mem: + 13 bytes [object.c:190 in fusion_object_pool_create()] -> 0x15448 " Surface Pool" (-) [Main Thread 0.447] ( 2182) Direct/Mem: + 136 bytes [object.c:179 in fusion_object_pool_create()] (-) [Main Thread 0.448] ( 2182) Direct/Mem: + 12 bytes [object.c:190 in fusion_object_pool_create()] -> 0x15460 " Window Pool" (-) [Main Thread 0.449] ( 2182) Core/Parts: Going to initialize 'clipboard_core' core... (-) [Main Thread 0.449] ( 2182) Direct/Mem: + 12 bytes [core_parts.c:68 in dfb_core_part_initialize()] (-) [Main Thread 0.450] ( 2182) Direct/Mem: + 112 bytes [core_parts.c:71 in dfb_core_part_initialize()] (-) [Main Thread 0.450] ( 2182) Core/Clipboard: dfb_clipboard_core_initialize( 0x16010, 0x15470, 0x16610 ) (-) [Main Thread 0.451] ( 2182) Core/Parts: Going to initialize 'colorhash_core' core... (-) [Main Thread 0.451] ( 2182) Direct/Mem: + 12 bytes [core_parts.c:68 in dfb_core_part_initialize()] (-) [Main Thread 0.452] ( 2182) Direct/Mem: + 104 bytes [core_parts.c:71 in dfb_core_part_initialize()] (-) [Main Thread 0.452] ( 2182) Core/ColorHash: dfb_colorhash_core_initialize( 0x16010, 0x15480, 0x16740 ) (-) [Main Thread 0.453] ( 2182) Core/Parts: Going to initialize 'surface_core' core... (-) [Main Thread 0.453] ( 2182) Direct/Mem: + 12 bytes [core_parts.c:68 in dfb_core_part_initialize()] (-) [Main Thread 0.454] ( 2182) Direct/Mem: + 16 bytes [core_parts.c:71 in dfb_core_part_initialize()] (-) [Main Thread 0.461] ( 2182) Core/SurfaceCore: dfb_surface_core_initialize( 0x16010, 0x16810, 0x16878 ) (-) [Main Thread 0.462] ( 2182) Core/SurfacePool: dfb_surface_pool_initialize( 0x400d7d20 ) (-) [Main Thread 0.462] ( 2182) Direct/Mem: + 264 bytes [surface_pool.c:136 in dfb_surface_pool_initialize()] (-) [Main Thread 0.463] ( 2182) Core/SurfacePool: init_pool( 0x168f0, 0x400d7d20 ) (-) [Main Thread 0.463] ( 2182) Direct/Mem: + 4 bytes [surface_pool.c:1038 in init_pool()] (-) [Main Thread 0.464] ( 2182) Direct/Mem: + 8 bytes [surface_pool.c:1045 in init_pool()] (-) [Main Thread 0.464] ( 2182) Direct/Mem: + 128 bytes [fake.c:54 in fusion_shm_pool_create()] (-) [Main Thread 0.465] ( 2182) Core/SurfacePool: => [0] 0x168f0 - 'Shared Memory' [0] (0), 0x400d7d20 (-) [Main Thread 0.466] ( 2182) Core/SurfacePool: dfb_surface_pool_initialize( 0x400d7ca8 ) (-) [Main Thread 0.466] ( 2182) Direct/Mem: + 264 bytes [surface_pool.c:136 in dfb_surface_pool_initialize()] (-) [Main Thread 0.467] ( 2182) Core/SurfacePool: init_pool( 0x16c80, 0x400d7ca8 ) (-) [Main Thread 0.467] ( 2182) Direct/Mem: + 20 bytes [surface_pool.c:1045 in init_pool()] (-) [Main Thread 0.468] ( 2182) Core/SurfacePool: => [0] 0x16c80 - 'System Memory' [1] (1), 0x400d7ca8 (-) [Main Thread 0.469] ( 2182) Core/SurfacePool: -> [1] 0x168f0 - 'Shared Memory' [0] (0), 0x400d7d20 (-) [Main Thread 0.793] ( 2182) Core/SurfacePool: dfb_surface_pool_initialize( 0x400d7ce4 ) (-) [Main Thread 0.794] ( 2182) Direct/Mem: + 264 bytes [surface_pool.c:136 in dfb_surface_pool_initialize()] (-) [Main Thread 0.795] ( 2182) Core/SurfacePool: init_pool( 0x16e88, 0x400d7ce4 ) (-) [Main Thread 0.795] ( 2182) Core/SurfacePool: -> [0] 0x16c80 - 'System Memory' [1] (1), 0x400d7ca8 (-) [Main Thread 0.795] ( 2182) Core/SurfacePool: -> [1] 0x168f0 - 'Shared Memory' [0] (0), 0x400d7d20 (-) [Main Thread 0.796] ( 2182) Core/SurfacePool: => [2] 0x16e88 - 'Preallocated Memory' [2] (0), 0x400d7ce4 (-) [Main Thread 0.797] ( 2182) Core/Parts: Going to initialize 'system_core' core... (-) [Main Thread 0.797] ( 2182) Direct/Mem: + 12 bytes [core_parts.c:68 in dfb_core_part_initialize()] (-) [Main Thread 0.797] ( 2182) Direct/Mem: + 320 bytes [core_parts.c:71 in dfb_core_part_initialize()] (-) [Main Thread 0.798] ( 2182) Core/System: dfb_system_core_initialize( 0x16010, 0x17008, 0x17070 ) (-) [Main Thread 0.799] ( 2182) Direct/Mem: + 24 bytes [fbdev.c:439 in system_initialize()] (-) [Main Thread 0.799] ( 2182) Direct/Mem: + 708 bytes [fbdev.c:445 in system_initialize()] (-) [Main Thread 0.800] ( 2182) FBDev/VT: dfb_vt_initialize() (-) [Main Thread 0.801] ( 2182) Direct/Mem: + 456 bytes [vt.c:111 in dfb_vt_initialize()] (-) [Main Thread 0.802] ( 2182) FBDev/VT: vt_get_fb( 2 ) (-) [Main Thread 0.803] ( 2182) FBDev/VT: -> 0 (-) [Main Thread 0.803] ( 2182) FBDev/VT: vt_set_fb( 2, -1 ) (-) [Main Thread 0.851] ( 2182) FBDev/VT: vt_init_switching() (-) [Main Thread 0.853] ( 2182) Direct/Thread: direct_thread_create( CRITICAL, 0x40340dc1((nil)), 'VT Switcher' ) (-) [Main Thread 0.854] ( 2182) Direct/Mem: + 120 bytes [thread.c:184 in direct_thread_create()] (-) [Main Thread 0.854] ( 2182) Direct/Mem: + 12 bytes [thread.c:191 in direct_thread_create()] -> 0x17918 " VT Switcher" (-) [Main Thread 0.855] ( 2182) Direct/Thread/Init: -> OTHER (-20) [0;0] (-) [Main Thread 0.856] ( 2182) Direct/Thread/Init: -> locking... (-) [Main Thread 0.857] ( 2182) Direct/Thread/Init: -> creating... (*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER 0/0] <8388608>... (-) [Main Thread 0.859] ( 2182) Direct/Thread/Init: -> waiting... (-) [ NO NAME 0.860] ( 2183) Direct/Thread/Init: direct_thread_main( 0x17818 ) <- tid 2183 (-) [ NO NAME 0.861] ( 2183) Direct/Thread/Init: -> starting... (-) [VT Switcher 0.862] ( 2183) Direct/Signals: Blocking all signals from now on! (-) [VT Switcher 0.862] ( 2183) Direct/Thread/Init: -> locking... (-) [VT Switcher 0.863] ( 2183) Direct/Thread/Init: -> signalling... (-) [VT Switcher 0.864] ( 2183) Direct/Thread/Init: -> unlocking... (-) [Main Thread 0.865] ( 2182) Direct/Thread/Init: -> ...thread is running. (-) [Main Thread 0.865] ( 2182) Direct/Thread/Init: -> unlocking... (-) [Main Thread 0.866] ( 2182) Direct/Thread/Init: -> returning 0x17818 (-) [VT Switcher 0.866] ( 2183) Direct/Thread/Init: -> running... (-) [VT Switcher 0.867] ( 2183) FBDev/VT: vt_thread( 0x17818, (nil) ) (-) [VT Switcher 0.867] ( 2183) FBDev/VT: ...vt_thread (signal -1) (-) [Main Thread 0.866] ( 2182) Direct/Thread: direct_thread_create( DEFAULT, 0x40341059((nil)), 'VT Flusher' ) (-) [Main Thread 0.869] ( 2182) Direct/Mem: + 120 bytes [thread.c:184 in direct_thread_create()] (-) [Main Thread 0.869] ( 2182) Direct/Mem: + 11 bytes [thread.c:191 in direct_thread_create()] -> 0x18190 " VT Flusher" (-) [Main Thread 1.192] ( 2182) Direct/Thread/Init: -> OTHER (0) [0;0] (-) [Main Thread 1.193] ( 2182) Direct/Thread/Init: -> locking... (-) [Main Thread 1.193] ( 2182) Direct/Thread/Init: -> creating... (*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0] <8388608>... (-) [Main Thread 1.195] ( 2182) Direct/Thread/Init: -> waiting... (-) [ NO NAME 1.196] ( 2184) Direct/Thread/Init: direct_thread_main( 0x18090 ) <- tid 2184 (-) [ NO NAME 1.196] ( 2184) Direct/Thread/Init: -> starting... (-) [VT Flusher 1.197] ( 2184) Direct/Signals: Blocking all signals from now on! (-) [VT Flusher 1.197] ( 2184) Direct/Thread/Init: -> locking... (-) [VT Flusher 1.197] ( 2184) Direct/Thread/Init: -> signalling... (-) [VT Flusher 1.199] ( 2184) Direct/Thread/Init: -> unlocking... (-) [Main Thread 1.199] ( 2182) Direct/Thread/Init: -> ...thread is running. (-) [Main Thread 1.200] ( 2182) Direct/Thread/Init: -> unlocking... (-) [Main Thread 1.200] ( 2182) Direct/Thread/Init: -> returning 0x18090 (*) DirectFB/FBDev: Found 's3c2410fb' (ID 0) with frame buffer at 0x33940000, 150k (MMIO 0x00000000, 0k) (-) [VT Flusher 1.201] ( 2184) Direct/Thread/Init: -> running... (-) [VT Flusher 1.202] ( 2184) FBDev/VT: vt_flush_thread( 0x18090, (nil) ) (-) [Main Thread 1.203] ( 2182) Direct/Mem: + 2048 bytes [fbdev.c:516 in system_initialize()] (-) [Main Thread 1.204] ( 2182) - - : DirectFB/FBDev: Could not retrieve palette for backup! (-) [Main Thread 1.204] ( 2182) Direct/Mem: - 2048 bytes [fbdev.c:535 in system_initialize()] -> 0x18908 'shared->orig_cmap_memory' (-) [Main Thread 1.205] ( 2182) Direct/Mem: + 2048 bytes [fbdev.c:539 in system_initialize()] (-) [Main Thread 1.205] ( 2182) Direct/Mem: + 2048 bytes [fbdev.c:552 in system_initialize()] (-) [Main Thread 1.214] ( 2182) - - : DirectFB/FBDev: couldn't access /proc/bus/pci/devices! (-) [Main Thread 1.215] ( 2182) Core/SurfacePool: dfb_surface_pool_initialize( 0x4034c010 ) (-) [Main Thread 1.215] ( 2182) Direct/Mem: + 264 bytes [surface_pool.c:136 in dfb_surface_pool_initialize()] (-) [Main Thread 1.216] ( 2182) Core/SurfacePool: init_pool( 0x199f8, 0x4034c010 ) (-) [Main Thread 1.217] ( 2182) Direct/Mem: + 8 bytes [surface_pool.c:1038 in init_pool()] (-) [Main Thread 1.217] ( 2182) Direct/Mem: + 8 bytes [surface_pool.c:1045 in init_pool()] (-) [Main Thread 1.218] ( 2182) FBDev/Surfaces: fbdevInitPool() (-) [Main Thread 1.218] ( 2182) SurfaceManager: dfb_surfacemanager_create( 0x16010, 153600 ) (-) [Main Thread 1.219] ( 2182) Direct/Mem: + 32 bytes [surfacemanager.c:83 in dfb_surfacemanager_create()] (-) [Main Thread 1.219] ( 2182) Direct/Mem: + 36 bytes [surfacemanager.c:87 in dfb_surfacemanager_create()] (-) [Main Thread 1.220] ( 2182) SurfaceManager: -> 0x19b28 (-) [Main Thread 1.220] ( 2182) Core/SurfacePool: -> [0] 0x16c80 - 'System Memory' [1] (1), 0x400d7ca8 (-) [Main Thread 1.221] ( 2182) Core/SurfacePool: -> [1] 0x168f0 - 'Shared Memory' [0] (0), 0x400d7d20 (-) [Main Thread 1.221] ( 2182) Core/SurfacePool: -> [2] 0x16e88 - 'Preallocated Memory' [2] (0), 0x400d7ce4 (-) [Main Thread Alignment trap: dfbinfo (2182) PC=0x40129e88 Instr=0x25004708 Address=0xfffff8f7 FSR 0x813 1.547] ( 2182) Core/SurfacePool: => [3] 0x199f8 - 'Frame Buffer Memory' [3] (0), 0x4034c010 (-) [Main Thread 1.548] ( 2182) Direct/Mem: + 24 bytes [screens.c:449 in dfb_screens_register()] (-) [Main Thread 1.548] ( 2182) Direct/Mem: + 464 bytes [layers.c:428 in dfb_layers_register()] (-) [Main Thread 1.549] ( 2182) Core/Parts: Going to initialize 'input_core' core... (-) [Main Thread 1.550] ( 2182) Direct/Mem: + 20 bytes [core_parts.c:68 in dfb_core_part_initialize()] (-) [Main Thread 1.550] ( 2182) Direct/Mem: + 72 bytes [core_parts.c:71 in dfb_core_part_initialize()] (-) [Main Thread 1.551] ( 2182) Core/Input: dfb_input_core_initialize( 0x16010, 0x19b50, 0x1b158 ) (-) [Main Thread 1.552] ( 2182) Direct/Modules: direct_modules_explore_directory( 'inputdrivers' ) (-) [Main Thread 1.555] ( 2182) Direct/Mem: + 44 bytes [modules.c:229 in direct_modules_explore_directory()] (-) [Main Thread 1.556] ( 2182) Direct/Mem: + 21 bytes [modules.c:237 in direct_modules_explore_directory()] -> 0x1c2c8 " libdirectfb_tslib.so" (-) [Main Thread 1.557] ( 2182) Direct/Modules: Loading '/usr/lib/directfb-1.4-0/inputdrivers/libdirectfb_tslib.so'... (-) [Main Thread 1.564] ( 2182) Direct/Modules: Registering 'tslib' ('inputdrivers')... (-) [Main Thread 1.564] ( 2182) Direct/Mem: + 6 bytes [modules.c:134 in direct_modules_register()] -> 0x1c708 " tslib" (-) [Main Thread 1.565] ( 2182) Direct/Modules: ...registered. (-) [Main Thread 1.565] ( 2182) Core/Input: init_devices( 0x16010 ) (-) [Main Thread 1.566] ( 2182) Direct/Mem: + 148 bytes [input.c:1219 in init_devices()] (-) [Main Thread 1.567] ( 2182) Core/Input: -> probing 'tslib Input Driver'... (-) [Main Thread 1.583] ( 2182) Direct/Mem: + 24 bytes [tslib.c:171 in driver_get_available()] -> 0x1b318 " /dev/input/touchscreen0" (!) [ 2182: 1.590] --> Caught signal 11 (at 0xfffff8f7, invalid address) <-- (-) [ 2182: -STACK- ] sh: nm: not found #0 0x400fae0d in ?? () from /usr/lib/libdirect-1.4.so.0 [0x400f0000] sh: nm: not found #1 0x41381cd1 in ?? () from /usr/lib/directfb-1.4-0/inputdrivers/libdirectfb_tslib.so [0x41381000] #2 0x413820ad in ?? () from /usr/lib/directfb-1.4-0/inputdrivers/libdirectfb_tslib.so [0x41381000] sh: nm: not found #3 0x40087a51 in ?? () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] #4 0x40087ef9 in ?? () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] #5 0x400b5c14 in dfb_core_part_initialize () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] #6 0x4007a375 in ?? () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] #7 0x4007a4cd in ?? () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] sh: nm: not found #8 0x400e4eac in fusion_arena_enter () from /usr/lib/libfusion-1.4.so.0 [0x400db000] #9 0x400b6014 in dfb_core_create () from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] sh: nm: not found #10 0x00008748 in DirectFBCreate () from dfbinfo [0x8000] #11 0x0000898d in abort () from dfbinfo [0x8000] (-) [ 2183: -STACK- ] sh: nm: not found #0 0x40340dc1 in ?? () from /usr/lib/directfb-1.4-0/systems/libdirectfb_fbdev.so [0x40336000] #1 0x40102075 in ?? () from /usr/lib/libdirect-1.4.so.0 [0x400f0000] (-) [ 2184: -STACK- ] #0 0x40341059 in ?? () from /usr/lib/directfb-1.4-0/systems/libdirectfb_fbdev.so [0x40336000] #1 0x40102075 in ?? () from /usr/lib/libdirect-1.4.so.0 [0x400f0000] (-) [Main Thread 1.789] ( 2182) DirectFB/Core: dfb_core_destroy... (-) [Main Thread 1.789] ( 2182) Direct/Signals: Removing handler 0x40079845 for signal -1 with context 0x16010... (-) [Main Thread 1.790] ( 2182) Direct/Mem: - 28 bytes [signals.c:176 in direct_signal_handler_remove()] -> 0x14f18 'handler' (-) [Main Thread 1.791] ( 2182) DirectFB/Core: Shutting down... (-) [Main Thread 1.792] ( 2182) Fusion/Object: == Window Pool == (-) [Main Thread 1.793] ( 2182) Fusion/Object: -> destroying pool... (-) [Main Thread 1.793] ( 2182) Fusion/Object: -> syncing... (-) [Main Thread 1.793] ( 2182) Fusion/Object: -> locking... (-) [Main Thread 1.794] ( 2182) Fusion/Object: -> pool destroyed (Window Pool) (-) [Main Thread 1.795] ( 2182) Direct/Mem: - 12 bytes [object.c:279 in fusion_object_pool_destroy()] -> 0x15460 'pool->name' (-) [Main Thread 1.795] ( 2182) Direct/Mem: - 136 bytes [object.c:280 in fusion_object_pool_destroy()] -> 0x16458 'pool' (-) [Main Thread 1.796] ( 2182) Fusion/Object: == Layer Region Pool == (-) [Main Thread 1.796] ( 2182) Fusion/Object: -> destroying pool... (-) [Main Thread 1.797] ( 2182) Fusion/Object: -> syncing... (-) [Main Thread 1.797] ( 2182) Fusion/Object: -> locking... (-) [Main Thread 1.798] ( 2182) Fusion/Object: -> pool destroyed (Layer Region Pool) (-) [Main Thread 1.798] ( 2182) Direct/Mem: - 18 bytes [object.c:279 in fusion_object_pool_destroy()] -> 0x15418 'pool->name' (-) [Main Thread 1.799] ( 2182) Direct/Mem: - 136 bytes [object.c:280 in fusion_object_pool_destroy()] -> 0x15320 'pool' (-) [Main Thread 1.799] ( 2182) Fusion/Object: == Layer Context Pool == (-) [Main Thread 1.800] ( 2182) Fusion/Object: -> destroying pool... (-) [Main Thread 2.124] ( 2182) Fusion/Object: -> syncing... (-) [Main Thread 2.124] ( 2182) Fusion/Object: -> locking... (-) [Main Thread 2.125] ( 2182) Fusion/Object: -> pool destroyed (Layer Context Pool) (-) [Main Thread 2.125] ( 2182) Direct/Mem: - 19 bytes [object.c:279 in fusion_object_pool_destroy()] -> 0x152a0 'pool->name' (-) [Main Thread 2.126] ( 2182) Direct/Mem: - 136 bytes [object.c:280 in fusion_object_pool_destroy()] -> 0x151a8 'pool' (-) [Main Thread 2.127] ( 2182) Fusion/Object: == Surface Pool == (-) [Main Thread 2.127] ( 2182) Fusion/Object: -> destroying pool... (-) [Main Thread 2.127] ( 2182) Fusion/Object: -> syncing... (-) [Main Thread 2.128] ( 2182) Fusion/Object: -> locking... (-) [Main Thread 2.128] ( 2182) Fusion/Object: -> pool destroyed (Surface Pool) (-) [Main Thread 2.129] ( 2182) Direct/Mem: - 13 bytes [object.c:279 in fusion_object_pool_destroy()] -> 0x15448 'pool->name' (-) [Main Thread 2.129] ( 2182) Direct/Mem: - 136 bytes [object.c:280 in fusion_object_pool_destroy()] -> 0x162f8 'pool' (-) [Main Thread 2.130] ( 2182) Fusion/Object: == Palette Pool == (-) [Main Thread 2.130] ( 2182) Fusion/Object: -> destroying pool... (-) [Main Thread 2.130] ( 2182) Fusion/Object: -> syncing... (-) [Main Thread 2.131] ( 2182) Fusion/Object: -> locking... (-) [Main Thread 2.131] ( 2182) Fusion/Object: -> pool destroyed (Palette Pool) (-) [Main Thread 2.132] ( 2182) Direct/Mem: - 13 bytes [object.c:279 in fusion_object_pool_destroy()] -> 0x15430 'pool->name' (-) [Main Thread 2.132] ( 2182) Direct/Mem: - 136 bytes [object.c:280 in fusion_object_pool_destroy()] -> 0x16198 'pool' (-) [Main Thread 2.133] ( 2182) Core/Parts: Going to shutdown 'surface_core' core... (-) [Main Thread 2.133] ( 2182) Core/SurfaceCore: dfb_surface_core_shutdown( 0x16810, emergency ) (-) [Main Thread 2.134] ( 2182) Core/SurfacePool: dfb_surface_pool_destroy( 0x16e88, 'Preallocated Memory' [2] ) (-) [Main Thread 2.135] ( 2182) Direct/Mem: - 264 bytes [surface_pool.c:275 in dfb_surface_pool_destroy()] -> 0x16e88 'pool' (-) [Main Thread 2.135] ( 2182) Core/SurfacePool: dfb_surface_pool_destroy( 0x16c80, 'System Memory' [1] ) (-) [Main Thread 2.136] ( 2182) Direct/Mem: - 20 bytes [surface_pool.c:1117 in remove_pool_local()] -> 0x16e00 'pool_locals[pool_id]' (-) [Main Thread 2.137] ( 2182) Direct/Mem: - 264 bytes [surface_pool.c:275 in dfb_surface_pool_destroy()] -> 0x16c80 'pool' (-) [Main Thread 2.137] ( 2182) Core/SurfacePool: dfb_surface_pool_destroy( 0x168f0, 'Shared Memory' [0] ) (-) [Main Thread 2.138] ( 2182) Direct/Mem: - 128 bytes [fake.c:75 in fusion_shm_pool_destroy()] -> 0x16b78 'pool' (-) [Main Thread 2.463] ( 2182) Direct/Mem: - 4 bytes [surface_pool.c:264 in dfb_surface_pool_destroy()] -> 0x16a70 'pool->data' (-) [Main Thread 2.463] ( 2182) Direct/Mem: - 8 bytes [surface_pool.c:1117 in remove_pool_local()] -> 0x16af8 'pool_locals[pool_id]' (-) [Main Thread 2.464] ( 2182) Direct/Mem: - 264 bytes [surface_pool.c:275 in dfb_surface_pool_destroy()] -> 0x168f0 'pool' (-) [Main Thread 2.464] ( 2182) Direct/Mem: - 16 bytes [core_parts.c:163 in dfb_core_part_shutdown()] -> 0x16878 'core_part->data_shared' (-) [Main Thread 2.465] ( 2182) Direct/Mem: - 12 bytes [core_parts.c:166 in dfb_core_part_shutdown()] -> 0x16810 'core_part->data_local' (-) [Main Thread 2.465] ( 2182) Core/Parts: Going to shutdown 'system_core' core... (-) [Main Thread 2.465] ( 2182) Core/System: dfb_system_core_shutdown( 0x17008, emergency ) (-) [Main Thread 2.466] ( 2182) Direct/Mem: - 2048 bytes [fbdev.c:732 in system_shutdown()] -> 0x18908 'shared->temp_cmap_memory' (-) [Main Thread 2.467] ( 2182) Direct/Mem: - 2048 bytes [fbdev.c:735 in system_shutdown()] -> 0x19180 'shared->current_cmap_memory' (-) [Main Thread 2.467] ( 2182) Core/SurfacePool: dfb_surface_pool_destroy( 0x199f8, 'Frame Buffer Memory' [3] ) (-) [Main Thread 2.468] ( 2182) FBDev/Surfaces: fbdevDestroyPool() (-) [Main Thread 2.468] ( 2182) SurfaceManager: dfb_surfacemanager_destroy( 0x19b28 ) (-) [Main Thread 2.469] ( 2182) Direct/Mem: - 36 bytes [surfacemanager.c:131 in dfb_surfacemanager_destroy()] -> 0x1ad70 'chunk' (-) [Main Thread 2.469] ( 2182) Direct/Mem: - 32 bytes [surfacemanager.c:139 in dfb_surfacemanager_destroy()] -> 0x19b28 'manager' (-) [Main Thread 2.470] ( 2182) Direct/Mem: - 8 bytes [surface_pool.c:264 in dfb_surface_pool_destroy()] -> 0x19b08 'pool->data' (-) [Main Thread 2.470] ( 2182) Direct/Mem: - 8 bytes [surface_pool.c:1117 in remove_pool_local()] -> 0x19b18 'pool_locals[pool_id]' (-) [Main Thread 2.471] ( 2182) Direct/Mem: - 264 bytes [surface_pool.c:275 in dfb_surface_pool_destroy()] -> 0x199f8 'pool' (-) [Main Thread 2.472] ( 2182) FBDev/VT: dfb_vt_shutdown() (-) [Main Thread 2.473] ( 2182) Direct/Thread: direct_thread_cancel( 0x40341059, 'VT Flusher' 2184 ) (-) [VT Flusher 2.475] ( 2184) Direct/Thread: direct_thread_cleanup( 0x40341059, 'VT Flusher' 2184 ) (-) [Main Thread 2.477] ( 2182) Direct/Thread: direct_thread_join( 0x40341059, 'VT Flusher' 2184 ) (-) [Main Thread 2.477] ( 2182) Direct/Thread: -> joining... (-) [Main Thread 2.479] ( 2182) Direct/Thread: -> joined. (-) [Main Thread 2.479] ( 2182) Direct/Thread: direct_thread_destroy( 0x40341059, 'VT Flusher' 2184 ) (-) [Main Thread 2.480] ( 2182) Direct/Mem: - 11 bytes [thread.c:618 in direct_thread_destroy()] -> 0x18190 'thread->name' (-) [Main Thread 2.807] ( 2182) Direct/Mem: - 120 bytes [thread.c:619 in direct_thread_destroy()] -> 0x18090 'thread' (-) [Main Thread 2.807] ( 2182) Direct/Thread: direct_thread_cancel( 0x40340dc1, 'VT Switcher' 2183 ) (-) [VT Switcher 2.809] ( 2183) Direct/Thread: direct_thread_cleanup( 0x40340dc1, 'VT Switcher' 2183 ) (-) [Main Thread 2.810] ( 2182) Direct/Thread: direct_thread_join( 0x40340dc1, 'VT Switcher' 2183 ) (-) [Main Thread 2.810] ( 2182) Direct/Thread: -> joining... (-) [Main Thread 2.811] ( 2182) Direct/Thread: -> joined. (-) [Main Thread 2.811] ( 2182) Direct/Thread: direct_thread_destroy( 0x40340dc1, 'VT Switcher' 2183 ) (-) [Main Thread 2.812] ( 2182) Direct/Mem: - 12 bytes [thread.c:618 in direct_thread_destroy()] -> 0x17918 'thread->name' (-) [Main Thread 2.812] ( 2182) Direct/Mem: - 120 bytes [thread.c:619 in direct_thread_destroy()] -> 0x17818 'thread' (-) [Main Thread 2.819] ( 2182) FBDev/VT: -> switching back... (-) [Main Thread 2.825] ( 2182) FBDev/VT: -> switched back... (-) [Main Thread 2.866] ( 2182) FBDev/VT: vt_set_fb( 2, 0 ) (-) [Main Thread 2.877] ( 2182) Direct/Mem: - 456 bytes [vt.c:324 in dfb_vt_shutdown()] -> 0x175d8 'dfb_vt' (-) [Main Thread 2.878] ( 2182) Direct/Mem: - 708 bytes [fbdev.c:753 in system_shutdown()] -> 0x172a0 'shared' (-) [Main Thread 2.878] ( 2182) Direct/Mem: - 24 bytes [fbdev.c:754 in system_shutdown()] -> 0x17218 'dfb_fbdev' (-) [Main Thread 2.880] ( 2182) Direct/Mem: - 320 bytes [core_parts.c:163 in dfb_core_part_shutdown()] -> 0x17070 'core_part->data_shared' (-) [Main Thread 2.880] ( 2182) Direct/Mem: - 12 bytes [core_parts.c:166 in dfb_core_part_shutdown()] -> 0x17008 'core_part->data_local' (-) [Main Thread 2.881] ( 2182) Core/Parts: Going to shutdown 'colorhash_core' core... (-) [Main Thread 2.881] ( 2182) Core/ColorHash: dfb_colorhash_core_shutdown( 0x15480, emergency ) (-) [Main Thread 2.902] ( 2182) Direct/Mem: - 104 bytes [core_parts.c:163 in dfb_core_part_shutdown()] -> 0x16740 'core_part->data_shared' (-) [Main Thread 2.903] ( 2182) Direct/Mem: - 12 bytes [core_parts.c:166 in dfb_core_part_shutdown()] -> 0x15480 'core_part->data_local' (-) [Main Thread 2.903] ( 2182) Core/Parts: Going to shutdown 'clipboard_core' core... (-) [Main Thread 2.904] ( 2182) Core/Clipboard: dfb_clipboard_core_shutdown( 0x15470, emergency ) (-) [Main Thread 2.904] ( 2182) Direct/Mem: - 112 bytes [core_parts.c:163 in dfb_core_part_shutdown()] -> 0x16610 'core_part->data_shared' (-) [Main Thread 2.905] ( 2182) Direct/Mem: - 12 bytes [core_parts.c:166 in dfb_core_part_shutdown()] -> 0x15470 'core_part->data_local' (-) [Main Thread 2.905] ( 2182) Direct/Mem: - 128 bytes [fake.c:75 in fusion_shm_pool_destroy()] -> 0x15120 'pool' (-) [Main Thread 2.906] ( 2182) Direct/Mem: - 120 bytes [core.c:1108 in dfb_core_arena_shutdown()] -> 0x15050 'shared' (-) [Main Thread 2.906] ( 2182) Direct/Mem: - 128 bytes [fake.c:75 in fusion_shm_pool_destroy()] -> 0x14f78 'pool' (-) [Main Thread 2.915] ( 2182) Direct/Mem: - 128 bytes [fake.c:75 in fusion_shm_pool_destroy()] -> 0x14e48 'pool' (-) [Main Thread 2.916] ( 2182) Direct/Mem: - 2520 bytes [fusion.c:2530 in fusion_exit()] -> 0x14468 'world->shared' (-) [Main Thread 2.925] ( 2182) Direct/Mem: - 532 bytes [fusion.c:2534 in fusion_exit()] -> 0x15d60 'world' (-) [Main Thread 2.926] ( 2182) Direct/Main: direct_shutdown() called... (-) [Main Thread 2.927] ( 2182) Direct/Main: ...2 references left. (-) [Main Thread 2.927] ( 2182) Direct/Mem: - 44 bytes [core.c:449 in dfb_core_destroy()] -> 0x16010 'core' Aborted From wadii.gd at gmail.com Tue Mar 9 14:00:04 2010 From: wadii.gd at gmail.com (Wadii Guedria) Date: Tue, 9 Mar 2010 14:00:04 +0100 Subject: [directfb-users] GTK-DFB Message-ID: <62af62821003090500q630896b9lea4a395dd06ee4c@mail.gmail.com> Hi all, I want to build GTK-DFB on Linux (fedora), not a cross compiling I dont know which steps to follow Thx wadii -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.harrold at gmail.com Tue Mar 9 15:29:17 2010 From: ian.harrold at gmail.com (Ian Harrold) Date: Tue, 9 Mar 2010 08:29:17 -0600 Subject: [directfb-users] Help, overlapping drawing In-Reply-To: <4B8FA859.70501@apexar.com> References: <4B8FA859.70501@apexar.com> Message-ID: <28a01671003090629j38a154fft2dc938439c0ed48b@mail.gmail.com> If the shape is an image I would put it on a new surface (Not sub-surface, which is sub portion of an existing layer) and then move the new layer around in coordinates. If I were to animate the shape, I would animate at each frame tick that new surface. DFB will flatten (z plane) the visible surfaces for you so they render properly, so you don't have to. On Thu, Mar 4, 2010 at 6:32 AM, Diego A. Fons wrote: > Hi, > > What's the best way of drawing a moving shape over an image? > > Right now I have an IDirectFBWindow and an IDirectFBImageProvider is > rendered in the window's surface, then I must draw a moving shape over this > image. > I tried getting a sub surface and drawing on it but I'm not able to clear > it because the image is cleared too (in a previous post I was able to > realise the problem). > Also I tried to create a new surface for drawing the moving shape and then > blit the surfaces, but the image is cleared and the result is a noisy image. > > So, can anyone help me on this issue? > > I hope you can understand my problem. > > Regards, > Diego A. Fons. > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.harrold at gmail.com Tue Mar 9 15:31:56 2010 From: ian.harrold at gmail.com (Ian Harrold) Date: Tue, 9 Mar 2010 08:31:56 -0600 Subject: [directfb-users] DirectFB installation issue In-Reply-To: <711056.97602.qm@web65501.mail.ac4.yahoo.com> References: <711056.97602.qm@web65501.mail.ac4.yahoo.com> Message-ID: <28a01671003090631s7cc91b01h60a97b176b2c10c6@mail.gmail.com> On Thu, Feb 25, 2010 at 9:23 PM, Jack W. wrote: > I just formatted the hard disk of my PC and reinstalled CentOS 5.4 and > directfb 1.4.1. But my old DirectFB programs can not run. I forget how I > figured out the DirectFB setting issues a half year ago. The error is due to > framebuffer device, I put them below. > > > [root at xpc070655 photowall]# ./showphotos > ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.1 |~~~~~~~~~~~~~~~~~~~~~~~~~~ > (c) 2001-2009 The world wide DirectFB Open Source Community > (c) 2000-2004 Convergence (integrated media) GmbH > ---------------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2010-02-25 21:20) > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment > variable. > (!) DirectFB/Core: Could not initialize 'system_core' core! > --> Initialization error! > (!) [ 3316: 0.069] --> Caught signal 11 (at 0x10, invalid address) <-- > Aborted > [root at xpc070655 photowall]# > > > I am looking for the solution. Thanks a lot for any help! > > -Jack > > > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > > According to the output, you cannot open the framebuffer. Try running as root and see if you have the same results. You may need to grant users rights to the fb device. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.harrold at gmail.com Tue Mar 9 15:36:05 2010 From: ian.harrold at gmail.com (Ian Harrold) Date: Tue, 9 Mar 2010 08:36:05 -0600 Subject: [directfb-users] DirectFB installation issue In-Reply-To: <711056.97602.qm@web65501.mail.ac4.yahoo.com> References: <711056.97602.qm@web65501.mail.ac4.yahoo.com> Message-ID: <28a01671003090636n7b246417r85bfc46f3dabf96e@mail.gmail.com> On Thu, Feb 25, 2010 at 9:23 PM, Jack W. wrote: > I just formatted the hard disk of my PC and reinstalled CentOS 5.4 and > directfb 1.4.1. But my old DirectFB programs can not run. I forget how I > figured out the DirectFB setting issues a half year ago. The error is due to > framebuffer device, I put them below. > > > [root at xpc070655 photowall]# ./showphotos > ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.1 |~~~~~~~~~~~~~~~~~~~~~~~~~~ > (c) 2001-2009 The world wide DirectFB Open Source Community > (c) 2000-2004 Convergence (integrated media) GmbH > ---------------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2010-02-25 21:20) > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment > variable. > (!) DirectFB/Core: Could not initialize 'system_core' core! > --> Initialization error! > (!) [ 3316: 0.069] --> Caught signal 11 (at 0x10, invalid address) <-- > Aborted > [root at xpc070655 photowall]# > > > I am looking for the solution. Thanks a lot for any help! > > -Jack > > > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > > Sorry for double posting, but perhaps I was too quick on my first reply. It appears you did run as root. I have never used CentOS, but here is some help from Ubuntu forums which may point you in the right direction. http://ubuntuforums.org/showthread.php?t=652038 Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From prageeth at msstyletech.co.jp Wed Mar 10 06:26:01 2010 From: prageeth at msstyletech.co.jp (Prageeth) Date: Wed, 10 Mar 2010 05:26:01 -0000 Subject: [directfb-users] Same PNG using DFB0.9.24 and DFB1.2.8 In-Reply-To: <002801cab925$a41c0a30$ec541e90$@co.jp> References: <002801cab925$a41c0a30$ec541e90$@co.jp> Message-ID: <005601cabfef$415c08c0$c4141a40$@co.jp> Hi All, It was found that setting the option pixelformat=RGB555 for the newer version will give a clear image, though such an option was not needed on the legacy DFB. Hope to get some explanation on the difference in behavior.. Thanks, Prageeth From: directfb-users-bounces at directfb.org [mailto:directfb-users-bounces at directfb.org] On Behalf Of Prageeth Sent: Monday, March 01, 2010 6:58 PM To: directfb-users at directfb.org Subject: [directfb-users] Same PNG using DFB0.9.24 and DFB1.2.8 Hi All, We are in the process of upgrading a legacy DirectFB-0.9.24 system to DirectFB-1.2.8, the later being built using buildroot-2009.05. However, the PNG test image looks better on the legacy DFB than on the newer version! On using IDirectFBSurface::Dump(), the destination surface for RenderTo(), and the final window surface to which Blit() is done, are both found to be same using legacy and new DFB. However, the primary layer's surface seems to differ as in attached ppm files. Moreover, the legacy version dumps a pgm file also. The DFB configuration of both systems were found to be same as attached. There is no hardware acceleration involved. Frame buffer settings given by fbset were also found to be same. However, the older 2.6.14.2 kernel had to be retained so that various device drivers could be reused. Hope using an older kernel need not be an issue. Any suggestions or debugging tips would be of great help. Thanks, Prageeth -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedro.aguilar.iniestra at gmail.com Fri Mar 12 22:07:37 2010 From: pedro.aguilar.iniestra at gmail.com (Pedro Aguilar) Date: Fri, 12 Mar 2010 22:07:37 +0100 Subject: [directfb-users] GTK-DFB In-Reply-To: <62af62821003090500q630896b9lea4a395dd06ee4c@mail.gmail.com> References: <62af62821003090500q630896b9lea4a395dd06ee4c@mail.gmail.com> Message-ID: <1268428057.16899.8.camel@uxmal> Hi, In the DirectFB Wiki you can find the instructions for building GTK-DFB for cross-compiling. Those instructions can be used for doing a native compilation. Basically, you will have to skip several steps like editing the Makefile for glib and other specific things for cross-compiling like the --host and --target parameters. It's not difficult to identify the parts that are cross-compiling specific and that you'll have to avoid. Regards. -- Pedro Aguilar http://www.paguilar.org On Tue, 2010-03-09 at 14:00 +0100, Wadii Guedria wrote: > Hi all, > > > I want to build GTK-DFB on Linux (fedora), not a cross compiling > I dont know which steps to follow > > > Thx > wadii > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users From andyturner74 at yahoo.com Fri Mar 12 21:35:40 2010 From: andyturner74 at yahoo.com (Andy Turner) Date: Fri, 12 Mar 2010 12:35:40 -0800 (PST) Subject: [directfb-users] DrawLine() more than one pixel thick In-Reply-To: <28a01671003090631s7cc91b01h60a97b176b2c10c6@mail.gmail.com> Message-ID: <933624.3275.qm@web62208.mail.re1.yahoo.com> ? Is there a way to draw lines more than one pixel thick under DirectFB? ? Thanks, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ci.faniq.com Sun Mar 14 14:52:45 2010 From: noreply at ci.faniq.com (Manikanta P) Date: Sun, 14 Mar 2010 14:52:45 +0100 Subject: [directfb-users] Manikanta P (vizzimani@gmail.com) has sent you a private message Message-ID: An HTML attachment was scrubbed... URL: From lathar at tataelxsi.co.in Mon Mar 15 05:16:19 2010 From: lathar at tataelxsi.co.in (Latha R) Date: Mon, 15 Mar 2010 09:46:19 +0530 Subject: [directfb-users] How to draw an OVAL using DFB? Message-ID: <1268626579.2720.2.camel@localhost.localdomain> Hi All, Can anybody please tell me how to draw an oval using directfb? I searched in DFB calls, there is no direct call....... :-( Thanks & Regards Latha R. From clebervinicius.eng at gmail.com Mon Mar 15 13:55:46 2010 From: clebervinicius.eng at gmail.com (Cleber Almeida) Date: Mon, 15 Mar 2010 10:55:46 -0200 Subject: [directfb-users] How can I to install DirectFB on ARM based board (AT91RM9200-EK) Message-ID: <5831d0461003150555w2d2f95e1t88089cc67aabf262@mail.gmail.com> Hi all, I'm new using DirectFB. Being thus, I'd like to install DirectFB 1.1.1, 1.0.0 or any version of DirectFB, on ARM based board AT91RM9200-EK. Someone have any script about it to help me? I got something using DirectFB-1.0.0, but I got problems after installing freetype2. Any programs that use fonts does not run! For example, df_andi and df_window. Thanks, Cleber Vin?cius Ribeiro de Almeida From mcmackerel at gmail.com Thu Mar 18 14:18:16 2010 From: mcmackerel at gmail.com (Asdf Ghjk) Date: Thu, 18 Mar 2010 14:18:16 +0100 Subject: [directfb-users] Quick boot and USB devices Message-ID: <1b0677171003180618m57fcdc53g4e12f210e66b3679@mail.gmail.com> Hi, I have a problem with my system booting so fast the USB subsystem hasn't detected my USB mouse/keyboard before CreateInputEventBuffer() is called, and so events from those devices don't get included. Is there some way to solve this problem that does not involve waiting for the devices to become available before initializing DirectFB? Thanks! From noreply at ci.faniq.com Sun Mar 21 14:46:16 2010 From: noreply at ci.faniq.com (Manikanta P) Date: Sun, 21 Mar 2010 14:46:16 +0100 Subject: [directfb-users] vizzimani@gmail.com has sent you a private message Message-ID: An HTML attachment was scrubbed... URL: From haithem.rahmani at gmail.com Wed Mar 24 16:53:00 2010 From: haithem.rahmani at gmail.com (haithem rahmani) Date: Wed, 24 Mar 2010 16:53:00 +0100 Subject: [directfb-users] Fwd: webkit-help Digest, Vol 9, Issue 24 In-Reply-To: References: Message-ID: <8160dd171003240853y62dc31c7q34166b7d73c2d9a2@mail.gmail.com> Hi Dennis, as you can see below there is a problem to implement WebKit plugins api for GTK-DirectFB backend. is there any plan to implement the missing api: gtk_socket_new and gtk_plug_new PS: it's now quite 2 weeks that I don't recieve mails from directfb mailing list what's going on ? regards. ---------- Forwarded message ---------- From: Date: Wed, Mar 24, 2010 at 3:00 PM Subject: webkit-help Digest, Vol 9, Issue 24 To: webkit-help at lists.webkit.org Send webkit-help mailing list submissions to webkit-help at lists.webkit.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.webkit.org/mailman/listinfo.cgi/webkit-help or, via email, send a message with subject or body 'help' to webkit-help-request at lists.webkit.org You can reach the person managing the list at webkit-help-owner at lists.webkit.org When replying, please edit your Subject line so it is more specific than "Re: Contents of webkit-help digest..." Today's Topics: 1. Re: flash player (Sriram Neelakandan) 2. Error in running ./autogen.sh on linux (hap 497) ---------------------------------------------------------------------- Message: 1 Date: Wed, 24 Mar 2010 10:28:50 +0530 From: Sriram Neelakandan To: thouraya andolsi Cc: webkit-help at lists.webkit.org Subject: Re: [webkit-help] flash player Message-ID: <2c778a731003232158t484f299fn913afd1ece6a1c76 at mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" - GTK/DFB port has not implemented a very important function that is used in Browser plugins. gtk_socket_new/gtk_plug_new Without these plugins will not work. For now, You have to create a custom DFB window and pass it down to the Plugin. Make changes in the plugin to accept this native DFB window via NPWindow IIRC qt-4.7 promises to provide a plugin solution for DFB, so hopefully that should set new standards for DFB based plugins On Mon, Mar 22, 2010 at 6:19 PM, thouraya andolsi < thouraya.andolsi at gmail.com> wrote: > Hi, > > I built the swfdec enabling gtk support and build the Swfdec-mozilla > removing the X dependencies and copied the "libswfdecmozilla.so" library > under the directory "/usr/lib/mozilla/plugins". > > Tried to run an html test showing a ".swf" file but I get a white window. > > Did any one succeded to get flash working in Webkit/GTK-Directfb? or > encountered such a problem ? > > Best regards, > Thouraya. > > > 2010/3/12 thouraya andolsi > > Hi, >> >> I would like to get flash working in webkit. >> I'm using Webkit/GTK-Directfb on linux. >> >> I built the swfdec but I don't have any idea on how to make flash working. >> >> Can any one help me ? >> >> Thanks in advance. >> >> Thouraya. >> > > > _______________________________________________ > webkit-help mailing list > webkit-help at lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-help > > -- Sriram Neelakandan Author - Embedded Linux System Design And Development ( http://tinyurl.com/2doosu) -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.webkit.org/pipermail/webkit-help/attachments/20100324/0c0a7681/attachment-0001.html > ------------------------------ Message: 2 Date: Wed, 24 Mar 2010 02:42:28 -0500 From: hap 497 To: webkit-help at lists.webkit.org Subject: [webkit-help] Error in running ./autogen.sh on linux Message-ID: <5ff1d48c1003240042i123fbd4cu11a793b1ec67593f at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, I have download Webkit source and tried to compile it under ubuntu 8.04. And I am following this https://trac.webkit.org/wiki/BuildingGtk to build, But I get this error: $ ./autogen.sh --enable-debug configure.ac:41: option `tar-ustar' not recognized Can you please tell me how to fix it? Thank you. ------------------------------ _______________________________________________ webkit-help mailing list webkit-help at lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-help End of webkit-help Digest, Vol 9, Issue 24 ****************************************** -- Say: He is God, the One and Only; God, the Eternal, Absolute; He begetteth not, nor is He begotten; And there is none like unto Him. -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels at directfb.org Sat Mar 27 10:25:57 2010 From: niels at directfb.org (Niels Roest) Date: Sat, 27 Mar 2010 12:25:57 +0300 Subject: [directfb-users] DirectFB installation issue In-Reply-To: <28a01671003090636n7b246417r85bfc46f3dabf96e@mail.gmail.com> References: <711056.97602.qm@web65501.mail.ac4.yahoo.com> <28a01671003090636n7b246417r85bfc46f3dabf96e@mail.gmail.com> Message-ID: <4BADCF25.4060802@directfb.org> Or, as a quick-test option, you can try to modprobe (as root) your graphics kernel module. On my system, this will cause udev to generate /dev/fb0 automatically. Generally, these are kept separate from the X-accelerators, and for met it's: /lib/modules/2.6.24-26-generic/kernel/drivers/video/matrox/ matroxfb_base.ko (ubuntu 9.10) Greets Niels Ian Harrold wrote: > > > On Thu, Feb 25, 2010 at 9:23 PM, Jack W. > wrote: > > I just formatted the hard disk of my PC and reinstalled CentOS 5.4 > and directfb 1.4.1. But my old DirectFB programs can not run. I > forget how I figured out the DirectFB setting issues a half year > ago. The error is due to framebuffer device, I put them below. > > > [root at xpc070655 photowall]# ./showphotos > ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.1 > |~~~~~~~~~~~~~~~~~~~~~~~~~~ > (c) 2001-2009 The world wide DirectFB Open Source Community > (c) 2000-2004 Convergence (integrated media) GmbH > ---------------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2010-02-25 21:20) > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER > environment variable. > (!) DirectFB/Core: Could not initialize 'system_core' core! > --> Initialization error! > (!) [ 3316: 0.069] --> Caught signal 11 (at 0x10, invalid > address) <-- > Aborted > [root at xpc070655 photowall]# > > > I am looking for the solution. Thanks a lot for any help! > > -Jack > > > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > > > Sorry for double posting, but perhaps I was too quick on my first > reply. It appears you did run as root. I have never used CentOS, but > here is some help from Ubuntu forums which may point you in the right > direction. > http://ubuntuforums.org/showthread.php?t=652038 > > Ian > > > ------------------------------------------------------------------------ > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" From niels at directfb.org Sat Mar 27 10:37:10 2010 From: niels at directfb.org (Niels Roest) Date: Sat, 27 Mar 2010 12:37:10 +0300 Subject: [directfb-users] Same PNG using DFB0.9.24 and DFB1.2.8 In-Reply-To: <002801cab925$a41c0a30$ec541e90$@co.jp> References: <002801cab925$a41c0a30$ec541e90$@co.jp> Message-ID: <4BADD1C6.6070707@directfb.org> Hi Prageeth, I had a look at the old-new pictures, and they look the same to me.. Can you be a bit clearer on what you mean with 'better'? I don't know straight off why you would not get a pgm though, although if you got it from a RGB16 than that would have been in error, so the newer version is correct in that sense. Greets Niels Prageeth wrote: > > Hi All, > > We are in the process of upgrading a legacy DirectFB-0.9.24 system to > DirectFB-1.2.8, the later being built using buildroot-2009.05. > However, the PNG test image looks better on the legacy DFB than on the > newer version! > > On using IDirectFBSurface::Dump(), the destination surface for > RenderTo(), and the final window surface to which Blit() is done, are > both found to be same using legacy and new DFB. However, the primary > layer?s surface seems to differ as in attached ppm files. Moreover, > the legacy version dumps a pgm file also. > > The DFB configuration of both systems were found to be same as > attached. There is no hardware acceleration involved. Frame buffer > settings given by fbset were also found to be same. However, the older > 2.6.14.2 kernel had to be retained so that various device drivers > could be reused. > > Hope using an older kernel need not be an issue. Any suggestions or > debugging tips would be of great help. > > Thanks, > > Prageeth > > ------------------------------------------------------------------------ > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" From niels at directfb.org Sat Mar 27 10:50:39 2010 From: niels at directfb.org (Niels Roest) Date: Sat, 27 Mar 2010 12:50:39 +0300 Subject: [directfb-users] Questions about blitting, hardware acceleration and the Linux framebuffer device In-Reply-To: <1b0677171003060522w759a4cd6x3eb45e7fbfaf46cc@mail.gmail.com> References: <1b0677171003060522w759a4cd6x3eb45e7fbfaf46cc@mail.gmail.com> Message-ID: <4BADD4EF.1080701@directfb.org> Asdf Ghjk wrote: > > This might be more related to blitting, hardware acceleration and the > Linux framebuffer in general, but as the answers might be interesting > to other people using DirectFB, I thought I'd ask anyway. > > > 1. When your source data is in main memory, what does > hardware-accelerated blitting do differently to achieve higher > performance? If the operation is just to copy data from main memory to > vram, then how could this ever be "accelerated"? > it could use DMA. If you simply use the 'bare' framebuffer device, which is available via mmap, then the data is always handled by the CPU. However, in general if you use acceleration, you stick the data in VRAM and use the video card hardware for moving-blitting-etcetera. > > 3. Is it possible to do a "real" page-flip on just the framebuffer > device without hardware acceleration, or will this just be implemented > by copying data from one region to another? > We rely on frame buffer ioctls to do this - the default fb driver creates a buffer twice the size of the display and does an ioctl-pan to and fro to simulate a flip. If this doesn't work we of course must copy using memcpy or equivalent. > > > Thanks! > > ------------------------------------------------------------------------ > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" From niels at directfb.org Sat Mar 27 11:01:41 2010 From: niels at directfb.org (Niels Roest) Date: Sat, 27 Mar 2010 13:01:41 +0300 Subject: [directfb-users] mini2440 TSLIB - caught signal 11 when running dfbinfo In-Reply-To: <1268000675.3238.17.camel@ed-hp-laptop> References: <1268000675.3238.17.camel@ed-hp-laptop> Message-ID: <4BADD785.9070406@directfb.org> Hi Ed, seems like you've managed to get quite far already. Apparently it crashes somewhere in libdirect (not libdirectfb) but without more specific location info it is going to be hard to tell the problem. I am not aware of any known issues there. It would be helpful to eg. use gdb or gdbserver, or do an strace, or put additional prints in libdirectfb_tslib to narrow down. Greets Niels ed wrote: > I am trying to get DirectFB running on the mini2440. > I am using openembedded to create my image. > In the directfb_1.4.2.bb file I have entered the following in the extra > OE configure section. > > EXTRA_OECONF = "\ > --enable-debug \ > --enable-trace \ > --enable-extra-warnings \ > --with-inputdrivers=tslib \ > --enable-fbdev \ > --enable-freetype=yes \ > --enable-zlib \ > --with-gfxdrivers=none \ > --disable-sdl \ > --disable-vnc \ > --disable-x11 \ > TSLIB_CFLAGS=\"-I${INSTALL_PATH}/include\" \ > TSLIB_LIBS=\"-L${INSTALL_PATH}/lib\" \ > " > > On the mini2440 I have exported the following variables. > export TSLIB_TSDEVICE=/dev/input/touchscreen0 > export TSLIB_CALIBFILE=/etc/pointercal > export TSLIB_PLUGINDIR=/usr/lib/ts > export TSLIB_CONFFILE=/etc/ts.conf > > I created a directfbrc file in /etc with the following lines. > memcpy=libc > debug > debugmem > debugshm > trace > > I ran ts_calibrate to configure display before running dfbinfo. > > Verified that there is a symbolic link from event1 to touchscreen0. > root at mini2440:/dev/input# ls -l > crw-r----- 1 root root 13, 64 Mar 7 23:19 event0 > crw-r----- 1 root root 13, 65 Mar 7 23:19 event1 > crw-r----- 1 root root 13, 63 Mar 7 23:19 mice > crw-r----- 1 root root 13, 32 Mar 7 23:19 mouse0 > lrwxrwxrwx 1 root root 6 Mar 7 23:19 touchscreen0 -> > event1 > > But when I run dfbinfo the program crashes right after probing tslib > input driver. > > Below is the output. > > ANY IDEAS ?????? > ============================================================ > > (-) [Main Thread 1.583] ( 2182) Direct/Mem: > + 24 bytes [tslib.c:171 in driver_get_available()] -> 0x1b318 > " /dev/input/touchscreen0" > (!) [ 2182: 1.590] --> Caught signal 11 (at 0xfffff8f7, invalid > address) <-- > (-) [ 2182: -STACK- ] > sh: nm: not found > #0 0x400fae0d in ?? () from /usr/lib/libdirect-1.4.so.0 [0x400f0000] > sh: nm: not found > #1 0x41381cd1 in ?? () > from /usr/lib/directfb-1.4-0/inputdrivers/libdirectfb_tslib.so > [0x41381000] > #2 0x413820ad in ?? () > from /usr/lib/directfb-1.4-0/inputdrivers/libdirectfb_tslib.so > [0x41381000] > sh: nm: not found > #3 0x40087a51 in ?? () from /usr/lib/libdirectfb-1.4.so.0 > [0x40025000] > #4 0x40087ef9 in ?? () from /usr/lib/libdirectfb-1.4.so.0 > [0x40025000] > #5 0x400b5c14 in dfb_core_part_initialize () > from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] > #6 0x4007a375 in ?? () from /usr/lib/libdirectfb-1.4.so.0 > [0x40025000] > #7 0x4007a4cd in ?? () from /usr/lib/libdirectfb-1.4.so.0 > [0x40025000] > sh: nm: not found > #8 0x400e4eac in fusion_arena_enter () > from /usr/lib/libfusion-1.4.so.0 [0x400db000] > #9 0x400b6014 in dfb_core_create () > from /usr/lib/libdirectfb-1.4.so.0 [0x40025000] > sh: nm: not found > #10 0x00008748 in DirectFBCreate () from dfbinfo [0x8000] > #11 0x0000898d in abort () from dfbinfo [0x8000] > > > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > > -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" From dok at directfb.org Sat Mar 27 21:47:44 2010 From: dok at directfb.org (Denis Oliver Kropp) Date: Sat, 27 Mar 2010 21:47:44 +0100 Subject: [directfb-users] Fwd: webkit-help Digest, Vol 9, Issue 24 In-Reply-To: <8160dd171003240853y62dc31c7q34166b7d73c2d9a2@mail.gmail.com> References: <8160dd171003240853y62dc31c7q34166b7d73c2d9a2@mail.gmail.com> Message-ID: <4BAE6EF0.3060408@directfb.org> haithem rahmani wrote: > Hi Dennis, > > as you can see below there is a problem to implement WebKit plugins > api for GTK-DirectFB backend. > is there any plan to implement the missing api: > > gtk_socket_new and gtk_plug_new I think it should not be too difficult to add it. Are you hobbyist or could the work be funded if you don't do it yourself? > PS: it's now quite 2 weeks that I don't recieve mails from directfb > mailing list > what's going on ? It is fixed now. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" From lindo at tataelxsi.co.in Mon Mar 29 06:43:17 2010 From: lindo at tataelxsi.co.in (Lindo Lonappan) Date: Mon, 29 Mar 2010 10:13:17 +0530 Subject: [directfb-users] Some General doubt about fusion in DirectFB-1.0.0 Message-ID: <4BB02FE5.6010107@tataelxsi.co.in> Dear All, I am using DirectFB-1.0.0. From the code and Google, we found that IDirectFB interface is a singleton one. So the subsequent call to the DirectFBInit() will simply return without changing any configuration and DirectFBCreate() call will return a reference to first IDirectFB handler. Our questions are, 1. We are configured, DirectFB as single core mode(ie without any fusion module). Is this is sufficient even if there is multiple DirectFBInit/DirectFBCreate call from the same applications? 2. Can we control the z-order of windows in this case also? (The two windows are created from two different references) 3. If above is possible can any one lead me to the APIs for that? (Both at the time of Creating new window and at run time) 4. Is fusion always necessary if there is multilple applications over DFB? (I read, it is required for IPCs. Can anyone explain a little more details) 5. Inside fusion module, there is a mmap() which using a flag MAP_FIXED. In our system the addresses it tries to map is already used by some other one and we are not able to free that. So is there any way to change this fixed address need?? Thanks a lot for your valuable time. -- Thanks& Regards, Lindo Lonappan. From lindo at tataelxsi.co.in Mon Mar 29 06:59:17 2010 From: lindo at tataelxsi.co.in (Lindo Lonappan) Date: Mon, 29 Mar 2010 10:29:17 +0530 Subject: [directfb-users] [directfb-dev] Some General doubt about fusion in DirectFB-1.0.0 In-Reply-To: <55b3397a1003272009r26317905o5e1245fd9f8bd921@mail.gmail.com> References: <4BA214FF.4030802@tataelxsi.co.in> <55b3397a1003272008x355a3c5bt9235672e46315317@mail.gmail.com> <55b3397a1003272009r26317905o5e1245fd9f8bd921@mail.gmail.com> Message-ID: <4BB033A5.20300@tataelxsi.co.in> Dear Shivakumar, Thanks for your reply. Sorry for posting the same mail again in user's list. It's a mistake from me. Dear Shivakumar/all, I am expecting more clarifications in Question number 4.( What is mean by smooth running. Is any crash/undefined behavious occur?) Can some one give me some explanation for Question number 5. Thanks & Regards, Lindo Lonappan. On 3/28/2010 8:39 AM, Shivakumar Mishra wrote: > > > On Sun, Mar 28, 2010 at 8:38 AM, Shivakumar Mishra > > wrote: > > hi, > > On Thu, Mar 18, 2010 at 5:26 PM, Lindo Lonappan > > wrote: > > Dear All, > > I am using DirectFB-1.0.0. > > >From the code and Google, we found that IDirectFB interface > is a singleton one. > So the subsequent call to the DirectFBInit() will simply > return without changing any configuration > and DirectFBCreate() call will return a reference to first > IDirectFB handler. > > Our questions are, > > 1. We are configured, DirectFB as single core mode(ie without > any fusion module). > Is this is sufficient even if there is multiple > DirectFBInit/DirectFBCreate call from the same applications? > > You can call multiple times .But it will give you same instance.It > has no effect. > > 2. Can we control the z-order of windows in this case also? > (The two windows are created from two different references) > > Yes you can. > > > 3. If above is possible can any one lead me to the APIs for that? > (Both at the time of Creating new window and at run time) > > There are two ways:- > 1. Create window with different layer and SetLevel for that > layer(according to your requirement) > 2.You can use these api for specific window:- (If you want it > from window operation) > > SetStackingClass,Raise,RaiseToTop,Lower etc. go through link:- > http://directfb.org/docs/DirectFB_Reference_1_4/IDirectFBWindow.html > > > 4. Is fusion always necessary if there is multilple > applications over DFB? > (I read, it is required for IPCs. Can anyone explain a > little more details) > > No (But necessary for smoother running of applications). > > > 5. Inside fusion module, there is a mmap() which using a flag > MAP_FIXED. > In our system the addresses it tries to map is already used > by some other one and we are not able to free that. > So is there any way to change this fixed address need?? > > Thanks a lot for your valuable time. > > -- > Thanks & Regards, > Lindo Lonappan. > > > > _______________________________________________ > directfb-dev mailing list > directfb-dev at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > > > > -- > "The best way to find yourself is to lose yourself in the service > of others". > > Shiva The Great > > > > > -- > "The best way to find yourself is to lose yourself in the service of > others". > > Shiva The Great -------------- next part -------------- An HTML attachment was scrubbed... URL: From elezegarcia at yahoo.com.ar Mon Mar 29 20:47:49 2010 From: elezegarcia at yahoo.com.ar (=?iso-8859-1?Q?Ezequiel_Garc=EDa?=) Date: Mon, 29 Mar 2010 11:47:49 -0700 (PDT) Subject: [directfb-users] Using StackingClass and SetLevel from different processes Message-ID: <56387.88884.qm@web56204.mail.re3.yahoo.com> Hi everyone, I have the following situation. Two processes need to use DirectFB (v1.0) separately. This is, they will both call DirectFBInit & DirectFBCreate.?Each will be drawing its own window on the same layer and I want to control the ZOrder of them. In particular I want one of them to draw its window always on top of the other process's window.? I tried to get that using StackingClass and ZOrder, but it didn't work.? Is it even possible? Maybe I'm doing something wrong. Some directions will be very well received... Greetings, Ezequiel. Yahoo! Cocina Encontra las mejores recetas con Yahoo! Cocina. http://ar.mujer.yahoo.com/cocina/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lathar at tataelxsi.co.in Tue Mar 30 06:01:13 2010 From: lathar at tataelxsi.co.in (Latha R) Date: Tue, 30 Mar 2010 09:31:13 +0530 Subject: [directfb-users] DrawLine() more than one pixel thick In-Reply-To: <933624.3275.qm@web62208.mail.re1.yahoo.com> References: <933624.3275.qm@web62208.mail.re1.yahoo.com> Message-ID: <1269921673.2695.1.camel@localhost.localdomain> Hi Andy, This is Latha, Just draw a rectangle, for how much pixel thick u want ............ Thank You, Latha R On Fri, 2010-03-12 at 12:35 -0800, Andy Turner wrote: > > Is there a way to draw lines more than one pixel thick under DirectFB? > > Thanks, > Andy > > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users From directfb at tvetc.de Tue Mar 30 10:52:33 2010 From: directfb at tvetc.de (Karim 'Kasi Mir' Senoucci) Date: Tue, 30 Mar 2010 10:52:33 +0200 (CEST) Subject: [directfb-users] DirectFB and Intel GMA3150 graphics Message-ID: Hello everyone, for an application which uses DirectFB, we're currently using a Mini-ITX board with a GMA950 gfx chip which works fine with the intelfb kernel driver and the "Intel 830/845G/852GM/855GM/865G" driver in DirectFB (we're still using 1.2.0). Now, there is talk of switching to another mainboard, and the Intel D410PT came up, which uses a GMA3150 graphics module. Starting the application on that mainboard results in DirectFB using the software renderer and failing: --------------------------------------------------------------------- [2010-03-30 18:50:20] (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org) [2010-03-30 18:50:20] (*) direct_modules_explore_directory( \'/usr/lib/directfb-1.2-0/wm\' ) [2010-03-30 18:50:20] (*) Found Module: libdirectfbwm_default.so [2010-03-30 18:50:20] (*) Lookup by file: libdirectfbwm_default.so [2010-03-30 18:50:20] (*) D_ALLOC: libdirectfbwm_default.so [2010-03-30 18:50:20] (*) open_module() != NULL [2010-03-30 18:50:20] (*) module->enabled! [2010-03-30 18:50:20] (*) DirectFB/Core/WM: Default 0.3 (directfb.org) [2010-03-30 18:50:20] (*) FBDev/Surface: Allocated 1280x1024 32 bit RGB32 buffer (index 0) at offset 0 and pitch 5120. [2010-03-30 18:50:20] (!) DirectFB/FBDev: Panning display failed (x=0 y=0 ywrap=0 vbl=1)! [2010-03-30 18:50:20] --> Invalid argument --------------------------------------------------------------------- Thus, my question is: is the GMA3150 currently supported by (perhaps a newer version of) DirectFB, and/or is there anything planned or in the works for furture releases. Or is it a waste of time to try to get that board to work with DirectFB? Thanks in advance for any insight into the matter. Greetings Karim Senoucci From kalle465 at hotmail.com Wed Mar 31 11:34:57 2010 From: kalle465 at hotmail.com (Karl Berg) Date: Wed, 31 Mar 2010 11:34:57 +0200 Subject: [directfb-users] Testing VRAM size in DirectFB 1.4.x Message-ID: Hi, I have a small test application that used to determine how much VIDEO RAM that is available for DirectFB since some drivers fail to report the correct size. This application essentially tries to allocate as many surfaces (10-40k size) as possible until we run out of memory. This has worked fine on DirectFB 1.0 but after upgrading to 1.4.3 this does not work any more. I have tested this on one embedded device with HW acceleration and it just keeps creating surfaces far above the GFX heap limit and eventually crashes. Running the same application on x86 without HW acceleration shows similar behaviour. Since there are no VIDEO_RAM available to DirectFB I would expect the IDirectFB::CreateSurface function to fail with an error, that's what happened in DirectFB 1.0 at least. *code* DFBSurfaceDescription dsc; dsc.flags = DSDESC_WIDTH | DSDESC_HEIGHT | DSDESC_PIXELFORMAT | DSDESC_CAPS; dsc.width = WIDTH; dsc.height = HEIGHT; dsc.pixelformat = pixelformat; dsc.caps = DSCAPS_VIDEOONLY; vram_size = 0; while (true) { err = dfb->CreateSurface( dfb, &dsc, &dest ); if (err != DFB_OK) break; vram_size += pitch*HEIGHT; } print_result(vram_size); *end code* I read here in the forum that DirectFB doesn't allocate the surface buffer until a graphics operation is actually performed on the surface. I have tried to add a FillRectangle call in the loop but no success. Also specifying DSCAPS_STATIC_ALLOC for the surface gives no improvement. So what have changed between the tested versions and what does a solution looks like that works across DirectFB versions? Best regards, Karl _________________________________________________________________ Mejla p? krogen! Hotmail i mobilen. http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From umeshsu at TechMahindra.com Wed Mar 31 14:57:39 2010 From: umeshsu at TechMahindra.com (Umesh Suryawanshi) Date: Wed, 31 Mar 2010 18:27:39 +0530 Subject: [directfb-users] More details of DFBBufferThresholds fields... scale/units ? Message-ID: I couldn't locate any field description of structure DFBBufferThresholds. 1) What is the scale/units e.g. in millisecond or seconds etc? minimum_level: what value to set? is it to be given in % or buffer size in bytes? maximum_time : is it in milliseconds or seconds? 2) Is there any way to ignore data level when we use time based threshold and vice versa? ========================= typedef struct { DFBStreamCapabilities selection; /* Which of the Audio / Video are we setting? */ struct { unsigned int minimum_level; /* The level at which a DVPET_DATALOW event will be generated. */ unsigned int maximum_level; /* The level at which a DVPET_DATAHIGH event will be generated. */ unsigned int minimum_time; /* The level at which a DVPET_BUFFERTIMELOW event will be generated. */ unsigned int maximum_time; /* The level at which a DVPET_BUFFERTIMEHIGH event will be generated. */ } video; struct { unsigned int minimum_level; /* The level at which a DVPET_DATALOW event will be generated. */ unsigned int maximum_level; /* The level at which a DVPET_DATAHIGH event will be generated. */ unsigned int minimum_time; /* The level at which a DVPET_BUFFERTIMELOW event will be generated. */ unsigned int maximum_time; /* The level at which a DVPET_BUFFERTIMEHIGH event will be generated. */ } audio; } DFBBufferThresholds; ============================================================================================================================Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.============================================================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: From andre.draszik at st.com Wed Mar 31 15:46:08 2010 From: andre.draszik at st.com (Andre DRASZIK) Date: Wed, 31 Mar 2010 14:46:08 +0100 Subject: [directfb-users] Testing VRAM size in DirectFB 1.4.x In-Reply-To: References: Message-ID: <1270043168.18023.3.camel@bril0118.bri.st.com> Hi Karl, It is really unfortunate that CreateSurface() will not fail anymore when there's not enough memory. But doing a FillRectangle() certainly works for me... Therefore, a combination of CreateSurface() and FillRectangle() should really work with any version of DirectFB. Cheers, Andre' On Wed, 2010-03-31 at 11:34 +0200, Karl Berg wrote: > Hi, > > > I have a small test application that used to determine how much VIDEO > RAM that is available for DirectFB since some drivers fail to report > the correct size. This application essentially tries to allocate as > many surfaces (10-40k size) as possible until we run out of memory. > This has worked fine on DirectFB 1.0 but after upgrading to 1.4.3 this > does not work any more. > I have tested this on one embedded device with HW acceleration and it > just keeps creating surfaces far above the GFX heap limit and > eventually crashes. > Running the same application on x86 without HW acceleration shows > similar behaviour. Since there are no VIDEO_RAM available to DirectFB > I would expect the IDirectFB::CreateSurface function to fail with an > error, that's what happened in DirectFB 1.0 at least. > > > *code* > > > DFBSurfaceDescription dsc; > dsc.flags = DSDESC_WIDTH | DSDESC_HEIGHT | DSDESC_PIXELFORMAT | > DSDESC_CAPS; > dsc.width = WIDTH; > dsc.height = HEIGHT; > dsc.pixelformat = pixelformat; > dsc.caps = DSCAPS_VIDEOONLY; > > vram_size = 0; > while (true) > { > err = dfb->CreateSurface( dfb, &dsc, &dest ); > if (err != DFB_OK) > break; > > vram_size += pitch*HEIGHT; > } > > > print_result(vram_size); > > > *end code* > > > I read here in the forum that DirectFB doesn't allocate the surface > buffer until a graphics operation is actually performed on the > surface. I have tried to add a FillRectangle call in the loop but no > success. Also specifying DSCAPS_STATIC_ALLOC for the surface gives no > improvement. > > > So what have changed between the tested versions and what does a > solution looks like that works across DirectFB versions? > > > Best regards, > > > Karl > > > ______________________________________________________________________ > L?s och svara p? mejl direkt i mobilen! Klicka h?r! > _______________________________________________ > directfb-users mailing list > directfb-users at directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users