On Mon, Mar 24, 2014 at 06:20:35PM -0700, Matt Roper wrote:
> On Wed, Mar 19, 2014 at 12:57:21PM +0100, Daniel Vetter wrote:
> > On Tue, Mar 18, 2014 at 05:22:53PM -0700, Matt Roper wrote:
> > > Now that CRTC's have a primary plane, there's no need to track the
> > > framebuffer in the CRTC. Repla
On Wed, Mar 19, 2014 at 12:57:21PM +0100, Daniel Vetter wrote:
> On Tue, Mar 18, 2014 at 05:22:53PM -0700, Matt Roper wrote:
> > Now that CRTC's have a primary plane, there's no need to track the
> > framebuffer in the CRTC. Replace all references to the CRTC fb
> > with the primary plane's fb.
>
On Tue, Mar 18, 2014 at 05:22:53PM -0700, Matt Roper wrote:
> Now that CRTC's have a primary plane, there's no need to track the
> framebuffer in the CRTC. Replace all references to the CRTC fb
> with the primary plane's fb.
>
> Also note that this simplifies framebuffer removal slightly; we no
>
Now that CRTC's have a primary plane, there's no need to track the
framebuffer in the CRTC. Replace all references to the CRTC fb
with the primary plane's fb.
Also note that this simplifies framebuffer removal slightly; we no
longer need to scan all CRTC's and disable the ones that were using the
