From: Takashi Iwai <tiwai@suse.de>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Max Staudt" <mstaudt@suse.de>, <michal@markovi.net>,
<b.zolnierkie@samsung.com>, "Michal Srb" <MSrb@suse.com>,
"Oliver Neukum" <ONeukum@suse.com>,
"Stefan Dirsch" <sndirsch@suse.com>,
<linux-fbdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 00/14] Kernel based bootsplash
Date: Thu, 09 Nov 2017 13:42:51 +0100 [thread overview]
Message-ID: <s5hr2t7ei7o.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171109115655.GA18436@atrey.karlin.mff.cuni.cz>
On Thu, 09 Nov 2017 12:56:55 +0100,
Pavel Machek wrote:
>
> Hi!
>
> > Dear fbdev and fbcon developers,
> >
> > Could you please voice your opinion on the following patch series?
> >
> >
> > This series adds simple bootsplash functionality on top of fbcon.
> >
> > A (simple!) kernel based bootsplash allows system integrators to show an
> > earlier and more reliable bootsplash, completely hiding the kernel's
> > text output and VT (the 'quiet' option still displays warnings and a
> > blinking cursor).
>
> "More reliable bootsplash" seems like an anti-goal. More reliable boot
> should be the goal...
>
> You should be able to display nice splash screen from initrd...
>
> We may want to fix the blinking cursor.
>
> But if there are warnings, it is better to see the warnings then to
> hide them. If root filesystem can't be mounted (for example) it is
> good to know the reason, not to stare at the blank screen (or at boot splash).
In theory, we can put a bootsplash_disable() call automatically when
the certain level of kernel message appears, too. It's a question
whether such behavior should be dynamically configurable or not,
though.
BTW, one thing that is bad with quiet boot option is that it hides
always messages and shows only errors. With this bootsplash scenario,
you can boot without quiet option. Once when the splash turned off
(either by user action like key input or by some kernel trigger),
you'll see the whole messages, thus have far more information there.
thanks,
Takashi
prev parent reply other threads:[~2017-11-09 12:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 12:45 [RFC 00/14] Kernel based bootsplash Max Staudt
2017-10-25 12:45 ` [RFC 01/14] bootsplash: Initial implementation showing black screen Max Staudt
2017-10-25 17:26 ` Randy Dunlap
2017-10-25 12:45 ` [RFC 02/14] bootsplash: Add platform device Max Staudt
2017-10-25 12:45 ` [RFC 03/14] bootsplash: Flush framebuffer after drawing Max Staudt
2017-10-25 12:45 ` [RFC 04/14] bootsplash: Redraw on suspend/hibernate Max Staudt
2017-10-25 12:45 ` [RFC 05/14] bootsplash: Disable splash on oops Max Staudt
2017-10-25 12:45 ` [RFC 06/14] bootsplash: Disable on SysRq SAK Max Staudt
2017-10-25 12:45 ` [RFC 07/14] bootsplash: Add VT keyboard hook Max Staudt
2017-10-25 12:45 ` [RFC 08/14] bootsplash: Add file reading and picture rendering Max Staudt
2017-10-25 17:32 ` Randy Dunlap
2017-10-25 20:27 ` Takashi Iwai
2017-10-27 11:21 ` Max Staudt
2017-10-25 12:45 ` [RFC 09/14] bootsplash: Add corner positioning Max Staudt
2017-10-25 12:45 ` [RFC 10/14] bootsplash: Add animation support Max Staudt
2017-10-25 17:20 ` Randy Dunlap
2017-10-25 17:23 ` Max Staudt
2017-10-25 12:45 ` [RFC 11/14] bootsplash: Redraw fully on console_unblank Max Staudt
2017-10-25 12:46 ` [RFC 12/14] bootsplash: Add sysfs ABI documentation Max Staudt
2017-10-25 12:46 ` [RFC 13/14] bootsplash: Add main documentation Max Staudt
2017-10-25 17:43 ` Randy Dunlap
2017-10-27 11:19 ` Max Staudt
2017-10-27 16:48 ` Randy Dunlap
2017-10-25 12:46 ` [RFC 14/14] bootsplash: Update MAINTAINERS Max Staudt
2017-11-09 11:56 ` [RFC 00/14] Kernel based bootsplash Pavel Machek
2017-11-09 12:36 ` Oliver Neukum
2017-11-09 18:45 ` Pavel Machek
2017-11-10 16:53 ` Takashi Iwai
2017-11-09 12:42 ` Takashi Iwai [this message]
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=s5hr2t7ei7o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=MSrb@suse.com \
--cc=ONeukum@suse.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@markovi.net \
--cc=mstaudt@suse.de \
--cc=pavel@ucw.cz \
--cc=sndirsch@suse.com \
/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).