From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"drivers, Intel" <Intel-gfx@lists.freedesktop.org>
Subject: Re: Flicker-free boot in DRM
Date: Sat, 29 Oct 2011 14:54:16 -0700 [thread overview]
Message-ID: <yunwrbn31mf.fsf@aiko.keithp.com> (raw)
In-Reply-To: <e39f63$2fuo92@fmsmga002.fm.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]
On Sat, 29 Oct 2011 09:12:13 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sat, 29 Oct 2011 00:05:22 -0700, "Keith Packard" <keithp@keithp.com> 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.
Yeah, I'm getting quite the light show at present, could well be due to
this.
> Best case failure is garbage during takeover; worst case is a GPU hang.
Sounds like creating a GEM object that maps stolen pages is not just a
good idea, but actually necessary.
With that and the mode detection, I think we'll be pretty much set
then. The two patches I've got now are sufficient to get from boot
through X only using mode_set_base, albeit with the screen transitioning
through some pretty crazy looking stuff.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-10-29 21:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 7:05 Flicker-free boot in DRM Keith Packard
2011-10-29 8:12 ` Chris Wilson
2011-10-29 21:54 ` Keith Packard [this message]
2011-10-30 4:24 ` Keith Packard
2011-10-31 16:56 ` Adam Jackson
2011-10-31 18:43 ` Keith Packard
2011-10-31 18:59 ` Adam Jackson
2011-10-31 16:57 ` Jesse Barnes
2011-10-31 18:45 ` Keith Packard
2011-10-31 17:00 ` Adam Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yunwrbn31mf.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.