2008/10/6 Oliver Gabel <[EMAIL PROTECTED]>:
> James Hughes wrote:
>>
>> I also have fairly specific question that someone must be able to
>> answer. If a function is NOT implemented in a driver (e.g. FillRect),
>> and DirectFB falls back to software rendering - how does that data get
>> to the LCD framebuffer? Does it then go via /dev/fb?
>
> The system maps either /dev/fb ("fbdev" system) or /dev/mem
> ("devmem" system) to the process' memory space via the mmmap()
> system call (functions MapMemAndReg(...) in
> DirectFB/systems/devmem/devmem.c
> and system_initialize(...) in DirectFB/systems/fbdev/fbdev.c respectively).
> Then it's just a question of writing to the framebuffer, i.e. to shared
> memory.
> This is implemented in DirectFB's virtual GPU "Genefx" AKA "Generic Graphix"
> AKA "Software Rasterizer" implemented in /src/gfx/generic/generic.c
> (drawing functions) and /src/gfx/generic/generic_dummy.c (dummy graphics
> driver).
> Please read the sources:
> http://git.directfb.org/?p=core/DirectFB.git;a=tree
>
> Hope this helps.
> Oliver
>
Thanks, that does help. From that I assume that since our LCD
framebuffer memory cannot be directly mapped in to host space memory,
I would need to implement the entire function set so DirectFB has no
need for devfb or devmem? Or will there always be circumstances where
DirectFB needs access to these?
James
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
