search for: dma_heap

...but I did not find any mentions that CREATE_DUMB should only be used for RGB buffers. Is anyone outside the core developers even aware of it? If we don't use dumb buffers there, where do we get the buffers? Maybe from a v4l2 device or from a gpu device, but often you don't have those. DMA_HEAP is there, of course. So we have the option to get DMA_HEAP buffers, specifying just the size of the buffer. Here we only specify the size, so the userspace has to understand the requirements for the format and the platform. Or we can use CREATE_DUMB, specifying the width, height and bitsperpix...

Hi Am 15.01.25 um 15:20 schrieb Tomi Valkeinen: [...] > > My point is that we have the current UAPI, and we have userspace using > it, but we don't have clear rules what the ioctl does with specific > parameters, and we don't document how it has to be used. > > Perhaps the situation is bad, and all we can really say is that > CREATE_DUMB only works for use with

...entions that CREATE_DUMB > should only be used for RGB buffers. Is anyone outside the core > developers even aware of it? > > If we don't use dumb buffers there, where do we get the buffers? Maybe > from a v4l2 device or from a gpu device, but often you don't have those. > DMA_HEAP is there, of course. Why can't there be a variant that takes a proper fourcc format instead of an imprecise bpp value? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with...

...> should only be used for RGB buffers. Is anyone outside the core > > developers even aware of it? > > > > If we don't use dumb buffers there, where do we get the buffers? Maybe > > from a v4l2 device or from a gpu device, but often you don't have those. > > DMA_HEAP is there, of course. > > Why can't there be a variant that takes a proper fourcc format instead of > an imprecise bpp value? Backwards compatibility. We can add an IOCTL for YUV / etc. But userspace must be able to continue allocating YUV buffers through CREATE_DUMB. > > Gr{o...

...y be used for RGB buffers. Is anyone outside the core >>> developers even aware of it? >>> >>> If we don't use dumb buffers there, where do we get the buffers? Maybe >>> from a v4l2 device or from a gpu device, but often you don't have those. >>> DMA_HEAP is there, of course. >> Why can't there be a variant that takes a proper fourcc format instead of >> an imprecise bpp value? > Backwards compatibility. We can add an IOCTL for YUV / etc. [...] > But userspace must be able to continue allocating YUV buffers through > CREAT...

...utside the core >>>> developers even aware of it? >>>> >>>> If we don't use dumb buffers there, where do we get the buffers? Maybe >>>> from a v4l2 device or from a gpu device, but often you don't have >>>> those. >>>> DMA_HEAP is there, of course. >>> Why can't there be a variant that takes a proper fourcc format >>> instead of >>> an imprecise bpp value? >> Backwards compatibility. We can add an IOCTL for YUV / etc. > > [...] > >> But userspace must be able to conti...

...s even aware of it? >>>>> >>>>> If we don't use dumb buffers there, where do we get the buffers? >>>>> Maybe >>>>> from a v4l2 device or from a gpu device, but often you don't have >>>>> those. >>>>> DMA_HEAP is there, of course. >>>> Why can't there be a variant that takes a proper fourcc format >>>> instead of >>>> an imprecise bpp value? >>> Backwards compatibility. We can add an IOCTL for YUV / etc. >> >> [...] >> >>> But u...