dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Vikas Patil <vikasmpatil-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: wayland mailing list
	<wayland-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Linux: Smooth splashscreen with system having weston with drm-backend
Date: Thu, 13 Jul 2017 19:03:44 +0530	[thread overview]
Message-ID: <CA+kt3u34G_wNFoCtBjX=mg9GcLaAcKxTZBdjt8txnrHgdqSRwA@mail.gmail.com> (raw)

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.

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

             reply	other threads:[~2017-07-13 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 13:33 Vikas Patil [this message]
     [not found] ` <CA+kt3u34G_wNFoCtBjX=mg9GcLaAcKxTZBdjt8txnrHgdqSRwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-13 13:50   ` Linux: Smooth splashscreen with system having weston with drm-backend 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
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='CA+kt3u34G_wNFoCtBjX=mg9GcLaAcKxTZBdjt8txnrHgdqSRwA@mail.gmail.com' \
    --to=vikasmpatil-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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).