On Wed, Sep 16, 2015 at 04:23:35PM +0100, Daniel Stone wrote: > The biggest issue though, is that this driver should become an atomic > modesetting driver. Atomic modesetting, rather than sending small > individual commands (enable CRTC, change plane position, etc) is based > on validating and passing around complete sets of hardware state. > Daniel Vetter's blog has an article on how to convert your driver: > http://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html Yeah, any new driver should really be built on top of atomic - it's a lot more flexible than the old thing and it's also what you want long-term. I've also just done a presenation about atomic for drivers: http://people.freedesktop.org/~danvet/presentations/xdc-2015.pdf Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
