On Wed, Mar 29, 2017 at 02:05:26PM -0700, Sinclair Yeh wrote:
> Hi Daniel,
>
> On Tue, Mar 28, 2017 at 09:49:38AM +0200, Daniel Vetter wrote:
> > On Mon, Mar 27, 2017 at 03:01:03PM -0700, Sinclair Yeh wrote:
> > > Switch over to using internal atomic API for mode set.
> > >
> > > This removes the
Hi Daniel,
On Tue, Mar 28, 2017 at 09:49:38AM +0200, Daniel Vetter wrote:
> On Mon, Mar 27, 2017 at 03:01:03PM -0700, Sinclair Yeh wrote:
> > Switch over to using internal atomic API for mode set.
> >
> > This removes the legacy set_config API, replacing it with
> > drm_atomic_helper_set_config()
On Mon, Mar 27, 2017 at 03:01:03PM -0700, Sinclair Yeh wrote:
> Switch over to using internal atomic API for mode set.
>
> This removes the legacy set_config API, replacing it with
> drm_atomic_helper_set_config(). The DRM helper will use various
> vmwgfx-specific atomic functions to set a mode.
Switch over to using internal atomic API for mode set.
This removes the legacy set_config API, replacing it with
drm_atomic_helper_set_config(). The DRM helper will use various
vmwgfx-specific atomic functions to set a mode.
DRIVER_ATOMIC capability flag is not yet set, so the user mode
will sti
