Hi,
I am new to DirectFB hacking though I have been using it for a few years
as a graphical backend for embedded targets.
I have an existing WebKit port that runs on top of either directfb (3
blitter-based embedded targets) or open gles (1 GPU-based embedded
target). The port itself is a fork of OWB (Orygin Web Browser), and uses
extensively the OWB Browser Abstraction Layer to "hide" target specifics.
Since owb has now gone closed source, I am looking for a replacement,
and WebKitDFB seems the perfect candidate for my three "traditional"
directfb targets, but I would like also to support the fourth (For
information, there is also a directfb driver that emulates a blitter for
that target, but it is really slow and buggy).
Looking at DirectFB internals, I came up with the idea of developing a
dedicated gfxdriver that:
1 - provides an EGL surface pool to override DirectFB core surface pool
(this part has unfortunately to be target-specific),
2 - performs all 2D operations on these internal surfaces through Open
GLES (this is generic).
Now, I am not 100% sure this is actually feasible, especially the first
part (though I have seen on this list that people have tried something
similar on the TI OMAP 3). What do you think ?
This done, another issue would be to have access to the underlying EGL
surfaces to be able to do some 3D rendering directly into them (the main
use-case is WebKit Canvas3D, ie WebGL). Looking at the IDirectFBGL
interface it may do the trick, but I am not sure ...
Anyway, advices from people more experienced than I am with DirectFB
internals would be much appreciated !
Thanks In Advance
David Corvoysier
Orange Labs
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
