gAcquire sets
gfxs->dst_org[0] = state->dst.addr;
Aop_xy sets
gfxs->Aop[0] = gfxs->dst_org[0];
ABacc_prepare does
void *ABstart = D_MALLOC( size * sizeof(GenefxAccumulator) * 2 +
31 );
So as far as I can see, genefx uses direct virtual address of the surfaces
in order to read/write data. It usually reads data into an internal
accumulation buffer which is malloced off the system heap, does pixel data
processing ("run pipeline") there (at 16bit per component), and finally
packs it back into the destination surface again with direct virtual address
access. All this per span.
What you want sounds like EXA pixmap migration in XOrg. Doesn't seem like
there's an equivalent in DFB.
2008/11/13 Nigel Hsiung <[EMAIL PROTECTED]>
> Hi list,
>
> First of all, my thanks to those involved in the "A couple of quick
> questions‏" discussion, its very helpful.
>
> I have another few questions - say my card does not support drawing lines,
> Directfb falls back to using software to draw the lines. The final result is
> written to the framebuffer mmap. But before being mmap to the framebuffer,
> is the line held in a temporary working buffer while clipping or does the
> software drawing operation directly manipulates the framebuffer mmap?
>
> If there is such a buffer, where is the buffer defined in the struct
> CardState or struct GenefxState? Can this buffer be converted to a blit
> source for hardware blitting?
>
> I am using Directfb-1.0 and looked at generic.c but couldnt yet figure out
> how genefx drawing works.
>
> thanks,
> Nigel
>
>
> ------------------------------
> Discover the new Windows Vista Learn
> more!<http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>
> _______________________________________________
> directfb-users mailing list
> [email protected]
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
>
>
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
