|Site sponsored by IGEL|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[directfb-dev] Re: how to assure a video-only surface
Quoting Antonino Daplas (firstname.lastname@example.org): > Hi, > > I'm trying to develop a gfxdriver for the i810 chipset. I already have > a working framebuffer driver, and most of the example directfb programs > work in generic fallback mode. Cool, could you point me to the location of the framebuffer driver? > My question is, how can I assure that the surfaces are "video-only"? > The card can only do hardware drawings/blittings if both the destination > and source are in framebuffer memory. I checked that there is a policy > flag CSP_VIDEOONLY. Is there a way to set this flag during hardware > initialization (driver_init)? Graphics drivers can assume that the surface is currently in video memory; before the driver gets called the surface management assures a valid video memory instance. For the destination "surface->back_buffer->video.*" is valid and to be programmed. For the source "surface->front_buffer->video.*" is valid and to be programmed. > I've just got the source for a few days so I haven't really studied the > source code. Have a look at the NeoMagic and the Matrox driver. -- Denis Oliver Kropp ( convergence ) ( integrated media gmbh ) -- Info: To unsubscribe send a mail to email@example.com with "unsubscribe directfb-dev" as subject.