From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: oselas@community.pengutronix.de
Cc: ptxdist@pengutronix.de
Subject: [ptxdist] GTK+ on DirectFB
Date: Thu, 26 Jan 2012 11:13:51 +0100 [thread overview]
Message-ID: <CABDcavYPyFQdPaaNH2Y1EB0NcqvMAJJCuLYtW-o3_D-c1uJ4XQ@mail.gmail.com> (raw)
Hello all,
I'm trying to test GTK+ on top of DirectFB on the mini2440 (2011.12.0).
I'm CCing the ptxdist ML in case this is not mini2440 specific.
I have built DirectFB with framebuffer support, and tslib and
linuxinput as input drivers. This works fine: I can run most of the
df_xxx examples (e.g. df_input, df_window, df_dok..)
I can also run GTK+ when built for the X.Org target.
However if I build GTK+ for the DirectFB target, the testgtk example
clears the screen, then crashes. Here's the output:
root@mini2440:~ testgtk
** (process:739): WARNING **: Couldn't find file "testgtkrc".
commandline read: testgtk
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.3
|~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2009 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2012-01-26 09:34)
(*) Direct/Memcpy: Using armasm_memcpy()
(*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER
0/0] <8388608>...
(*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0]
<8388608>...
(*) DirectFB/FBDev: Found 's3c2410fb' (ID 0) with frame buffer at
0x33940000, 150k (MMIO 0x00000000, 0k)
(*) Direct/Thread: Started 'tslib Input' (-1) [INPUT OTHER/OTHER 0/0]
<8388608>...
(*) DirectFB/Input: tslib touchscreen 0 0.1 (tslib)
(*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0]
<8388608>...
(*) DirectFB/Input: gpio-keys 0.1 (directfb.org)
(*) Direct/Thread: Started 'Keyboard Input' (-1) [INPUT OTHER/OTHER
0/0] <8388608>...
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(testgtk:739): Gdk-CRITICAL **: IA__gdk_drawable_set_colormap:
assertion `cmap == NULL || gdk_drawable_get_depth (drawable) == cmd
(*) Direct/Thread: Started 'EventBufferFeed' (-1) [MESSAGING
OTHER/OTHER 0/0] <8388608>...
(!) [ 739: 0.000] --> Caught signal 11 (at 0x28, invalid address)
<--
(!!!) *** WARNING [still objects in 'Window Pool'] *** [object.c:241
in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Region Pool'] ***
[object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Context Pool'] ***
[object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Surface Pool'] ***
[object.c:241 in fusion_object_pool_destroy()]
Aborted
Can anyone share any experiences on this?
Thanks,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-01-26 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 10:13 Guillermo Rodriguez Garcia [this message]
2012-01-26 10:32 ` [ptxdist] [oselas] " Juergen Beisert
2012-01-26 12:31 ` Guillermo Rodriguez Garcia
2012-01-26 12:50 ` Juergen Beisert
2012-01-26 15:45 ` Guillermo Rodriguez Garcia
2012-01-26 10:35 ` [ptxdist] " Robert Schwebel
2012-01-26 12:40 ` Guillermo Rodriguez Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABDcavYPyFQdPaaNH2Y1EB0NcqvMAJJCuLYtW-o3_D-c1uJ4XQ@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=oselas@community.pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox