Hi, On 2 February 2017 at 07:41, Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx> wrote: > i915 is pretty much feature complete. Support for atomic i915-specific > connector properties is still missing; those properties can (for now) > only be set through the legacy ioctl. > > ILK style watermarks and gen9+ watermarks are handled atomically, > and nonblocking modesets work. FBC has also been made to work with > atomic. > > gen4x- and vlv/chv watermarks still need to be fixed, so disable atomic > by default there for now. > > Flip the switch!! Not until we have the multi-CRTC event support please. :\ I don't want to have divergent event paths for atomic-but-useless-events. I've been frantically typing up support for this in Weston (actual proper atomic modesetting, which is difficult when you have fiercely independent per-output repaint loops, but seems ~mostly done but for typing), which I'd hoped to have done a week or two ago but got derailed due to being sick. It's coming just as quickly as I can type it tho. Cheers, Daniel _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx