search for: xxx_create_gem

...ar. As a result, drivers that employing GEM DMA has no other choice, but to abuse the dumb buffer API to do allocation for the more complex format buffers. The dumb buffer API doesn't support to specify buffer format, tile status and placement etc. The more advance drivers has been exposed the xxx_create_gem() to user-space. It seems that a few more experienced programmers hint us to create an new ioctl at above thread, so that we can keep employing simple API to do simple things and to suit complex needs with the more advanced APIs. > ?Tomi > -- Best regards, Sui

...vers that employing GEM DMA has no other choice, but to abuse the > dumb buffer API to do allocation for the more complex format buffers. > > The dumb buffer API doesn't support to specify buffer format, tile status and > placement etc. The more advance drivers has been exposed the xxx_create_gem() > to user-space. It seems that a few more experienced programmers hint us to > create an new ioctl at above thread, so that we can keep employing simple API > to do simple things and to suit complex needs with the more advanced APIs. I'd really like to explore adding new ioctls to e...

On 19/01/2025 16:59, Sui Jingfeng wrote: >>>> But userspace must be able to continue allocating YUV buffers through >>>> CREATE_DUMB. >>> >>> I think, allocating YUV buffers through CREATE_DUMB interface is just >>> an *abuse* and *misuse* of this API for now. >>> >>> Take the NV12 format as an example, NV12 is YUV420 planar