10:49 <beeno> hello all. I see on my device that libgbm is linked to libmali. Is this normal?

10:58 <phh> beeno: why wouldn't it be?

10:59 <phh> (I would have thought that libgbm is libmali, like EGL/GLES/OpenCL libs)

11:05 <beeno> Hi phh, ok I wasn't sure if it was just a general lib, same as libdrm. So would you say it's always the gpu that provides this, same on platforms like x64?

11:18 <phh> beeno it's complicated. It is "the platform". Most people use drm/kms, so standard open-source libgbm is ok

11:19 <phh> But mali doesn't use drm, hence they need special gbm. But theorically speaking, you might need to change gbm for stuff like vpu

11:21 <beeno> ok so if I link to libgbm on the rk3288, and if I then recompile for x64 (let's say a ubuntu vm), then it should just work?

11:21 <wadim_> isn't the libgbm (provided by libmali) a "standard" libgbm interface?

11:54 <phh> wadim_ yup

11:54 <phh> beeno it should yes

15:34 <beeno> I now have my DRM page flipping working, but I'm getting tearing. It's running with the correct frame rate so clearly waiting on the page_flip_handler is working. Should I be calling any methods specific for vsync?

15:39 <beeno> the interesting thing is that tearing isn't a horizontal line but a bit of a staircase. that appears to be mali's tile rendering. do I need to specifically create 2 buffers or activate back buffer usage in DRM?

17:58 <beeno> to answer my own question. I had an issue in the code and was reusing the same buffer object which means I was rendering the front buffer. The double buffering has to be implemented in your own code