All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: Splashscreen using psplash
Date: Tue, 23 Apr 2013 14:07:17 +0100	[thread overview]
Message-ID: <1366722437.23738.59.camel@ted> (raw)
In-Reply-To: <51767FE1.5060809@mlbassoc.com>

On Tue, 2013-04-23 at 06:34 -0600, Gary Thomas wrote:
> On 2013-04-23 06:29, Andreas Enbacka wrote:
> > Hello,
> >
> > Thanks a lot for info, I will try with that.
> >
> > //Andreas
> >
> > -----Original Message-----
> > From: Burton, Ross [mailto:ross.burton@intel.com]
> > Sent: 23. huhtikuuta 2013 15:09
> > To: Andreas Enbacka
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] Splashscreen using psplash
> >
> > On 23 April 2013 13:03, Andreas Enbacka <aenbacka@gmail.com> wrote:
> >> I am creating a custom image based on core-image-sato, with a custom splash
> >> screen (using psplash). I have been able to replace the default yocto
> >> splashscreen in my image,  however, my question is whether it is possible to
> >> hide the initial console output text displayed on the screen prior to
> >> showing the splashscreen?  Currently most of the boot process is completed
> >> at the stage when the splash screen is being displayed on screen. This is
> >> because the image should be used as part of an embedded device, and the
> >> end-user should not see any traces of the underlying linux distro.
> >
> > Passing "quiet" to the kernel (APPEND+="quiet" in local.conf will do
> > it for testing) should stop the majority of the text.  A full
> > splash-from-bootloader is possible if you have a bootloader that
> > displays the image, and then a silent kernel from there.
> 
> Note: AFAICT this will only work if booting using grub or syslinux, not U-Boot
> or some other embedded bootstrap.

The trick is to redirect the console output somewhere else. By default
it goes to the first tty if I recall correctly but you can send it to a
serial port or wherever you want...

Cheers,

Richard






  reply	other threads:[~2013-04-23 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 12:03 Splashscreen using psplash Andreas Enbacka
2013-04-23 12:08 ` Gary Thomas
2013-04-23 12:09 ` Burton, Ross
2013-04-23 12:29   ` Andreas Enbacka
2013-04-23 12:34     ` Gary Thomas
2013-04-23 13:07       ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-19  6:58 Tian Wen See

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=1366722437.23738.59.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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 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.