Hi there.
Short answers below.
Asdf Ghjk wrote:
Hi,
I'm trying to wrap my head around DirectFB and am still confused over
a few things. Having the following questions answered would probably
clear things up for me:
1. Is the graphics driver necessary? Can DirectFB do its thing on just
the framebuffer device /dev/fb0?
no, yes.
2. How is /dev/fb0 used by DirectFB, and what's the interplay between
it and the graphics driver? If Linux already provides a framebuffer
hardware abstraction, then why is the driver necessary?
/dev/fb0 is used by the fbdev system. This is used to provide the
graphics drivers the necessary context, and it handles the
mmap/resolution change/flip abstraction towards DirectFB.
3. Where are graphics drivers stored? Can you change this directory?
How does DirectFB know which graphics driver to load? Are the graphics
drivers just loadable kernel modules?
The location is defined by what you pass during the ./configure step.
The graphics drivers are, by default, dynamic libraries that implement
GraphicsDriverFuncs (see gfxcard.h). All libraries are tried in turn. At
the moment a Probe() returns true, that library is used.
4. Which graphics driver should I use for QEMU emulating an x86
system? The emulated hardware specs can be found
at http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator .
If you do not need hardware acceleration or resolution changes, you can
try without a gfxdriver (you might encounter some small limitations).
Thanks!
------------------------------------------------------------------------
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
