dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Stone <daniel-rLtY4a/8tF1rovVCs/uTlw@public.gmane.org>
To: Matt Hoosier <matt.hoosier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>,
	Vikas Patil <vikasmpatil-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>,
	wayland mailing list
	<wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Linux: Smooth splashscreen with system having weston with drm-backend
Date: Mon, 17 Jul 2017 21:20:53 +0100	[thread overview]
Message-ID: <CAPj87rNg4jy3_5EVDT859=DZqO0avbT1G_ZyLqE_cyrSwGKyPw@mail.gmail.com> (raw)
In-Reply-To: <CAJgxT38Vc3cMd1jNPfjctLxrU_FSiJ5bYU5kEQih_x34=s_7Ew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Matt,

On 17 July 2017 at 20:39, Matt Hoosier <matt.hoosier@gmail.com> wrote:
> Also beware that the DRM backend of Weston will aggressively set the mode
> before you have any chance to paint user-defined content of your own in a
> Wayland client program. So there will still be some window of time during
> which your early splashscreen disappears and no specific application content
> replaces it.

Funnily enough, I'd say it's aggressively delayed. ;) It makes sure to
wait until the shell (usually desktop-shell) signals 'ready'. The 3.0
alpha just released should delay the modeset even further, to avoid a
flicker to black.

Cheers,
Daniel
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

  parent reply	other threads:[~2017-07-17 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 13:33 Linux: Smooth splashscreen with system having weston with drm-backend Vikas Patil
     [not found] ` <CA+kt3u34G_wNFoCtBjX=mg9GcLaAcKxTZBdjt8txnrHgdqSRwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-13 13:50   ` Daniel Vetter
     [not found]     ` <CAKMK7uFNwB+K0eFBwF-91oaxFNmoFOm9_A+pR3nP7_Y53DqT6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-14  9:37       ` Vikas Patil
2017-07-14 13:56         ` Daniel Vetter
     [not found]           ` <20170714135637.asemv5nebx6vi6jb-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-07-17 19:39             ` Matt Hoosier
     [not found]               ` <CAJgxT38Vc3cMd1jNPfjctLxrU_FSiJ5bYU5kEQih_x34=s_7Ew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-17 20:20                 ` Daniel Stone [this message]
2017-07-14 16:04     ` Sean Paul

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='CAPj87rNg4jy3_5EVDT859=DZqO0avbT1G_ZyLqE_cyrSwGKyPw@mail.gmail.com' \
    --to=daniel-rlty4a/8tf1rovvcs/utlw@public.gmane.org \
    --cc=daniel-/w4YWyX8dFk@public.gmane.org \
    --cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=matt.hoosier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=vikasmpatil-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).