From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [PATCH 2/5] drm/i915: retrieve current fb config into new plane_config structure at init Date: Thu, 14 Nov 2013 08:09:12 -0800 Message-ID: <20131114080912.6bfd65ef@jbarnes-desktop> References: <1384366848-845-1-git-send-email-jbarnes@virtuousgeek.org> <1384366848-845-3-git-send-email-jbarnes@virtuousgeek.org> <20131114150659.GF13207@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from oproxy4-pub.mail.unifiedlayer.com (oproxy4-pub.mail.unifiedlayer.com [74.220.216.66]) by gabe.freedesktop.org (Postfix) with SMTP id E9881FB0C1 for ; Thu, 14 Nov 2013 08:08:13 -0800 (PST) In-Reply-To: <20131114150659.GF13207@nuc-i3427.alporthouse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Thu, 14 Nov 2013 15:06:59 +0000 Chris Wilson wrote: > On Wed, Nov 13, 2013 at 10:20:45AM -0800, Jesse Barnes wrote: > > Read out the current plane configuration at init time into a new > > plane_config structure. This allows us to track any existing > > framebuffers attached to the plane and potentially re-use them in our > > fbdev code for a smooth handoff. > > I don't see where plane_config is freed afterwards? We just keep it around like a piece of stale toast... guess I need to find a place to free it (maybe after the first mode set or after the fbdev BIOS init). -- Jesse Barnes, Intel Open Source Technology Center