Albert Torras wrote: > Hi, > > I've had some problems with color using DirectFB on an ARM i.MX21, and I > can't find where it modifies the pointer to memory. > > What I want to do is to change the way data is transferred to the fbdev > memory... Anyone can help?
Most of the CPU access to the frame buffer happens in the software rendering code in src/gfx/generic/generic.c, but there's also some code in src/core/surfacemanager.c for "upload/download" of buffers. Another place is src/misc/gfx_util.c for scaling and converting (loaded) image data to the various formats a surface can have. Furthermore, applications can also access the framebuffer using the public API IDirectFBSurface::Lock(). Endianness problems? Or no direct mapping of the framebuffer? -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
