Hello Oliver, 
On Wed, 31 Mar 2010, Oliver Gabel wrote:

[...]
> The graphics drivers are in the "gfxdrivers" directory. There
> you'll find a subdirectory for every graphics driver that DirectFB supports.
> You'll see an "i810" and "i830" directory there, so these are the only chips
> that are currently supported. The directfb you get from git is always the
> bleeding-edge version :-)

I already visited the gfxdrivers directory; I just wanted to make sure 
that a) nobody else already implemented something like that outside of 
direcfb.org and b) none of the existing drivers work undocumentedly on 
the GMA3150. As I've had both experiences with other open-source 
projects in the past, I thought one e-mail woudn't hurt. :-)  

[...]
> Thus, if you want to use directfb with hardware acceleration on your
> board, you would have to port the relevant part of the xorg driver to
> DirectFB. Given that there is already a working xorg driver and given
> the hardware programming docs at intellinuxgraphics.org, this should be
> feasible :-)

I'm not all that experienced when it comes to driver programming under 
Linux (most of my software development is done on embedded systems 
without an operating system to speak of), but I will take a look and see 
if that can be managed in a reasonable amount of time. Do I just need a 
DirectFB gfxdriver, or would I neet a linux kernel frame buffer driver 
as well? The system which runs my application boots with frame buffer 
(depending on mainboard, either viafb, intelfb, or uvesafb) activated,
and I imagine there might be problems when the kernel uses uvesafb and 
DirectFB tries to access the device directly. 

But perhaps I don't even need hardware acceleration - the Atom isn't all 
that fast, but I'm just blitting a few images and write a few strings 
onto the display, nothing fancy. However, I don't really get why 
DirectFB woudln't even start: 

| [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)!

I just call the libary via 

| DirectFB::Init("--dfb:mode=1280x1024,depth=32,pixelformat=RGB32");

and create a double-buffered primary surface:

|  dsc.flags = DSDESC_CAPS;
|  DFB_ADD_SURFACE_CAPS( dsc.caps, DSCAPS_PRIMARY);
|  DFB_ADD_SURFACE_CAPS( dsc.caps, DSCAPS_VIDEOONLY);
|  DFB_ADD_SURFACE_CAPS( dsc.caps, DSCAPS_DOUBLE);
|  DFB_ADD_SURFACE_DESC(dsc.flags, DSDESC_PIXELFORMAT);
|  dsc.pixelformat= DSPF_RGB32;
|
|  primary=dfb->CreateSurface(dsc);

Is there any reason why this should fail like above when using the 
software rasterizer? And how can I get around that without hardware 
acceleration?

Greetings
Karim Senoucci


_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to