From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: Flicker-free boot in DRM Date: Sat, 29 Oct 2011 09:12:13 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTP id 584C19E7D0 for ; Sat, 29 Oct 2011 01:12:19 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Keith Packard , "drivers, Intel" List-Id: intel-gfx@lists.freedesktop.org On Sat, 29 Oct 2011 00:05:22 -0700, "Keith Packard" wrote: > * Constructing a fake drm_framebuffer is a pain; there are a million > places that assume all kinds of things about the frame buffer on > a crtc. This is vital as we need to capture the current GATT and stolen allocations and preserve them across takeover. Otherwise we end up using the VBIOS scanout PTEs as our ringbuffer and the actual memory for FBC. Best case failure is garbage during takeover; worst case is a GPU hang. -Chris -- Chris Wilson, Intel Open Source Technology Centre