From: Randy Dunlap <rdunlap@infradead.org>
To: Max Staudt <mstaudt@suse.de>,
b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org
Cc: tiwai@suse.com, oneukum@suse.com, msrb@suse.com,
sndirsch@suse.com, michal@markovi.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 01/14] bootsplash: Initial implementation showing black screen
Date: Wed, 25 Oct 2017 10:26:03 -0700 [thread overview]
Message-ID: <2e19f572-5850-ba1e-8b81-94c02c800094@infradead.org> (raw)
In-Reply-To: <20171025124602.28292-2-mstaudt@suse.de>
On 10/25/17 05:45, Max Staudt wrote:
> diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
> index 7f1f1fbcef9e..a6617c07229a 100644
> --- a/drivers/video/console/Kconfig
> +++ b/drivers/video/console/Kconfig
> @@ -151,6 +151,30 @@ config FRAMEBUFFER_CONSOLE_ROTATION
> such that other users of the framebuffer will remain normally
> oriented.
>
> +config BOOTSPLASH
> + bool "Bootup splash screen"
> + depends on FRAMEBUFFER_CONSOLE=y
Fix "help" indentation: (from process/coding-style:)
Lines under a ``config`` definition
are indented with one tab, while help text is indented an additional two
spaces.
> + ---help---
> + This option enables the Linux bootsplash screen.
> +
> + The bootsplash is a full-screen logo or animation indicating a
> + booting system. It replaces the classic scrolling text with a
> + graphical alternative, similar to other systems.
> +
> + Since this is technically implemented as a hook on top of fbcon,
> + it can only work if the FRAMEBUFFER_CONSOLE is enabled and a
> + framebuffer driver is active. Thus, to get a text-free boot,
> + the system needs to boot with vesafb, efifb, or similar.
> +
> + Once built into the kernel, the bootsplash needs to be enabled
> + with bootsplash.enabled=1 and a splash file needs to be supplied.
> +
> + Further documentation can be found in:
> + Documentation/fb/bootsplash.txt
> +
> + If unsure, say N.
> + This is typically used by distributors and system integrators.
> +
> config STI_CONSOLE
> bool "STI text console"
> depends on PARISC
--
~Randy
next prev parent reply other threads:[~2017-10-25 17:26 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 [this message]
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
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=2e19f572-5850-ba1e-8b81-94c02c800094@infradead.org \
--to=rdunlap@infradead.org \
--cc=b.zolnierkie@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@markovi.net \
--cc=msrb@suse.com \
--cc=mstaudt@suse.de \
--cc=oneukum@suse.com \
--cc=sndirsch@suse.com \
--cc=tiwai@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).