I'd like to re-open a previous discussion on this topic as I am having
the same error and none of the suggestions worked for me.
I have a GTK test application that works fine on the desktop, but when
cross-compiled for an ARM touchscreen only device, I get:
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.3.0
|~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2008 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2009-04-02 18:42)
(*) Direct/Memcpy: Using libc memcpy()
(*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER
0/0] <2093056>...
(*) Direct/Thread: Started 'Cowon_O2 TS Input' (-1) [INPUT
OTHER/OTHER 0/0] <2093056>...
(*) DirectFB/Input: o2pmp 0.1 (COWON)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(*) FBDev/Surface: Allocated 480x272 16 bit RGB16 buffer (index 0)
at offset 0 and pitch 960.
(#) DirectFBError [gdk_display_open: GetDisplayLayer]: Requested ID
not found!
(sliders.o2:254): Gtk-WARNING **: cannot open display:
All of the DirectFB test applications I've run, have worked fine. I am
using a new input driver that works with dfb_input, and I have also
applied Vince's patch for armasm_memcpy(). My directfbrc file contains:
system = fbdev
fbdev = /dev/fb
o2pmp-device = /dev/cwn
mode = 480x272
scaled = 480x272
depth = 16
pixelformat = RGB16
no-cursor # Disable Cursor
no-init-layer = 0 # Disable Layer Initialization
no-vt # Disable vt
no-vt-switch # Don't allow vt switching (redundant?)
smooth-upscale # Scaling
smooth-downscale
window-surface-policy = systemonly # Window surface swapping policy:
desktop-buffer-mode = backsystem # Desktop buffer mode:
memcpy=armasm # Use the ARM
optimized memcpy()
The output of dfbinfo is:
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.3.0
|~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2008 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2009-04-02 18:42)
(*) Direct/Memcpy: Using armasm_memcpy()
(*) Direct/Thread: Started 'VT Switcher' (260) [CRITICAL OTHER/OTHER
0/0] <2093056>...
(*) Direct/Thread: Started 'Cowon_O2 TS Input' (261) [INPUT
OTHER/OTHER 0/0] <2093056>...
(*) DirectFB/Input: o2pmp 0.1 (COWON)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(*) FBDev/Surface: Allocated 480x272 16 bit RGB16 buffer (index 0)
at offset 0 and pitch 960.
Screen (00) FBDev Primary Screen (primary screen)
Caps: VSYNC POWER_MANAGEMENT
Layer (00) FBDev Primary Layer (primary layer)
Type: GRAPHICS
Caps: SURFACE BRIGHTNESS CONTRAST SATURATION
Input (01) o2pmp (primary mouse)
Type: MOUSE
Caps: AXES BUTTONS
Max. Axis: 1
Max. Button: 0
The "no-vt" doesn't seem to be working, but I am at a loss as to what is
causing this. Is it due to there being no keyboard?
Any ideas on how I can go about fixing this?
Thanks much!
-fred
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
