Hi Ilyes, A video only surface (typically external) already is a physically contiguous memory buffer (normally/always AFAIK), and there already is the pixel format DSPF_A8 which is one byte that could be repurposed. So, I don't understand the need to create a new surface pixel format for a surface buffer that is NOT a surface, especially since the surface interface allows pixel based operations to be performed on it (blitting and drawing) and it can be flipped (allocation can be double/triple buffered).
Best Regards, Timothy -- Timothy Strelchun STB & SW Engineering PCCG Service Provider Division Intel Corporation >-----Original Message----- >From: directfb-dev-boun...@directfb.org [mailto:directfb-dev- >boun...@directfb.org] On Behalf Of Ilyes GOUTA >Sent: Wednesday, November 07, 2012 3:33 AM >To: directfb-dev@directfb.org >Subject: [directfb-dev] [PATCH] directfb: introduce the new DSPF_BYTE >opaque pixel format > >Hi, > >The attached patch defines a new DSPF_BYTE pixelformat allowing >DirectFB-based applications to allocate IDirectFBSurface(s) which are >backed by contiguous buffers in physical memory. These surfaces could >be used for transport such by loading data into these and passing them >to other devices (ex: h/w decoders). > >As these are still IDirectFBSurface(s) objects, DSPF_BYTE surfaces >then also benefit from all the internal functionality provided by >DirectFB such as reference counting, the integration w/ >IDirectFBDataBuffer and so on. > >Feedback is welcome. > >Regards, >-Ilyes _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
