Emma Anholt

@lromor That's not an error, please ignore it.

Hopefully https://github.com/raspberrypi/linux/pull/1835 fixes a bunch of instability around CMA OOMs. Could you test if you're still having trouble with that?

I think the problem there would be a frame that draws (say) a single pixel is unlikely to light up a pixel center of the downscaled image.

If you're using KMS directly, why not just map your dumb buffer and write the data directly into it in the first place, going from 1 or 2 copies with...

Have you actually measured and found that the memcpy call overhead is a problem compared to a single memcpy? Because I bet you'll have a difficult time measuring a difference....

Those sys\* are just for fbdev. We could probably accelerate fbdev using the dma engine, but nobody's built those helpers yet.

Actually, if you care about the number of memcpy loops, you could just make your drm_framebuffer have the stride that you want, and copy your whole buffer. vc4 doesn't have...

32 and 64 have no difference in their CMA requirements. I would guess that your 32 and 64 builds are getting different cma amounts chosen by the kernel, though (look...

freedesktop.org could use this, as it seems approvers aren't available in gitlab CE.

I think I've got this worked around with dropping --add-reviewers from the deploy.yml.