dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>
To: Vikas Patil <vikasmpatil-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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: Thu, 13 Jul 2017 15:50:56 +0200	[thread overview]
Message-ID: <CAKMK7uFNwB+K0eFBwF-91oaxFNmoFOm9_A+pR3nP7_Y53DqT6g@mail.gmail.com> (raw)
In-Reply-To: <CA+kt3u34G_wNFoCtBjX=mg9GcLaAcKxTZBdjt8txnrHgdqSRwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, Jul 13, 2017 at 3:33 PM, Vikas Patil <vikasmpatil@gmail.com> wrote:
> Dear All,
>
> I am looking for an solution to have early smooth splashscreen on the
> Linux system with Weston and drm-backend.
>
> I tried showing splashscreen using Linux logo and fbcon Linux features
> but it is not smooth as when system boots logo gets displayed via
> kernel and as the Weston starts
> I see flicker and blackscreen.
>
> Another approach I tried is having standalone drm api based
> application [1] which uses the one of the available hardware
> plane/overlay for displaying splash image and Weston is
> starting and uses default plane which is different from plane utilized
> by above application. but still I see flicker and black screen when
> Weston starts.
>
> I want splash to be displayed on one of the h/w plane and Weston
> should start in background without any flicker and black screen on
> some other plane.
>
> Anyone here before achieved such a use case with such system? Looking
> for inputs/suggestions/ideas to achieve this. It is ok if something
> needs to be hacked/changd at any level (kernel driver, weston).
>
> This is required on platform such as TI (Jacinto) and Intel (Broxton)
> or devices based on drm graphics stack.
>
> [1] http://git.ti.com/glsdk/example-applications/blobs/39080525baca7bf136f2412d62436366a736af6b/drm-tests/drm_z_alpha.c
>
> Thanking you all for your time and inputs in advance.

If you make sure you have matching modes between the 2 users of drm
this should work. kms drivers (especially if they are already
converted to atomic) will automatically optimize transitions to not
flicker (if possible).

If you still flicker then it's either a kernel driver issue, a hw
limitations (some hw needs a full modeset for e.g. changing the bit
depth) or you program two different things.

Also, you must ensure that the boot-splash does not quit until weston
has fully taken over, otherwise kms will first shut down the screen
(when the splash quits), then re-enable it when weston starts.

Cheers, Daniel

>
> Thanks & Regards,
> Vikash
> _______________________________________________
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

  parent reply	other threads:[~2017-07-13 13:50 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 [this message]
     [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
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=CAKMK7uFNwB+K0eFBwF-91oaxFNmoFOm9_A+pR3nP7_Y53DqT6g@mail.gmail.com \
    --to=daniel.vetter-/w4ywyx8dfk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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).