On Fri, Aug 05, 2016 at 11:04:21AM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 05.08.2016 10:15, Daniel Vetter wrote:
>
> Hi,
>
> > There's a driver cap DRM_CAP_DUMB_PREFER_SHADOW for this. If set,
> > render into a shadow buffer and copy over in bursts, otherwise you
> > can assume that
On 05.08.2016 10:15, Daniel Vetter wrote:
Hi,
> There's a driver cap DRM_CAP_DUMB_PREFER_SHADOW for this. If set,
> render into a shadow buffer and copy over in bursts, otherwise you
> can assume that the memory is fully cpu cached and fast with random
> access.
h!
nekrad at orion:~/src/lin
On Fri, Aug 05, 2016 at 04:35:25AM +0200, Enrico Weigelt, metux IT consult
wrote:
> Hi folks,
>
>
> when putting pixels into an DRM framebuffer, should I do that in
> bursts/blocks instead of byte-per-byte ? (eg. explicitly using
> aligned 32bit ops).
There's a driver cap DRM_CAP_DUMB_PREFER_SH
Hi folks,
when putting pixels into an DRM framebuffer, should I do that in
bursts/blocks instead of byte-per-byte ? (eg. explicitly using
aligned 32bit ops).
--mtx
