From: Max Staudt <mstaudt@suse.de> To: Jani Nikula <jani.nikula@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch> Cc: linux-fbdev@vger.kernel.org, michal@markovi.net, b.zolnierkie@samsung.com, sndirsch@suse.com, oneukum@suse.com, tiwai@suse.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, philm@manjaro.org, bernhard.rosenkranzer@linaro.org Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash Date: Wed, 3 Jan 2018 18:38:47 +0100 [thread overview] Message-ID: <af4600fc-ad5d-411c-d899-9fe557a79add@suse.de> (raw) In-Reply-To: <878tdlzccc.fsf@intel.com> On 12/29/2017 06:13 PM, Jani Nikula wrote: > I think the first issue is the boot manager (e.g. grub) messing up > whatever the BIOS or GOP or whatever drew. If I don't touch any buttons, > I'd prefer the Lenovo or VAIO or NUC or whatever logo stay there. IIRC > some BIOSes let you set up your own splash if you like, though that's > not really relevant for me. So already the boot manager takeover is a > problem. > > The next issue is the framebuffer driver takeover. It's not unlike the > above, just one step further. If you like your grub image to stay there, > let it stay there. (Or, if the boot manager was nice enough to not mess > up the screen, let the BIOS image stay there.) All the way to KMS and > userspace. > > IMHO the user friendly experience is already gone by the time we reach > any kernel/userspace bootsplash. We want our command-line tools to STFU > if they don't have anything interesting to say. As a user, 99.99+% of > the time I don't care what grub or dmesg have to say. Agreed - the kernel should go out of the user's way if they want it to be silent. It's already possible, as long as KMS is not in use (since that automatically sets a mode and thus usually clears the screen). What you want is really the opposite of the kernel splash, or any splash on top of Linux (kernel or userspace) at all. Returning to cases where a splash running on Linux may be desired: I see adding to the initial logo as an interesting use case. An animation to show that the kernel hasn't crashed while booting is quite useful. Something like adding a spinning wheel underneath the initial logo helps. Macs do (or used to do) that after showing the apple, IIRC. I think this is where something simple and kernel based is helpful, vs. something userspace based. Maybe they can even build on top of each other, just like LILO used to print each letter as a confirmation of successfully executing a part of itself. Thinking of it: Loading a KMS driver basically always necessitates a mode change on variable resolution platforms such as PCs. And changing mode requires clearing the screen. Now, what if we could preload the new framebuffer with a splash, rather than a blank screen? That's not generally feasible (for example, double buffering is an implicit requirement), but who knows, maybe in the future. Just an odd idea. > Of course, with the kernel developer hat on, I want all of the clues > every time in case something goes wrong. But this shouldn't have to be > mutually exclusive. I agree - that's why it's important to be able to disable the bootsplash by changing the kernel cmdline. Max
WARNING: multiple messages have this Message-ID (diff)
From: Max Staudt <mstaudt@suse.de> To: Jani Nikula <jani.nikula@linux.intel.com>, Daniel Vetter <daniel@ffwll.ch> Cc: linux-fbdev@vger.kernel.org, michal@markovi.net, b.zolnierkie@samsung.com, sndirsch@suse.com, oneukum@suse.com, tiwai@suse.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, philm@manjaro.org, bernhard.rosenkranzer@linaro.org Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash Date: Wed, 03 Jan 2018 17:38:47 +0000 [thread overview] Message-ID: <af4600fc-ad5d-411c-d899-9fe557a79add@suse.de> (raw) In-Reply-To: <878tdlzccc.fsf@intel.com> On 12/29/2017 06:13 PM, Jani Nikula wrote: > I think the first issue is the boot manager (e.g. grub) messing up > whatever the BIOS or GOP or whatever drew. If I don't touch any buttons, > I'd prefer the Lenovo or VAIO or NUC or whatever logo stay there. IIRC > some BIOSes let you set up your own splash if you like, though that's > not really relevant for me. So already the boot manager takeover is a > problem. > > The next issue is the framebuffer driver takeover. It's not unlike the > above, just one step further. If you like your grub image to stay there, > let it stay there. (Or, if the boot manager was nice enough to not mess > up the screen, let the BIOS image stay there.) All the way to KMS and > userspace. > > IMHO the user friendly experience is already gone by the time we reach > any kernel/userspace bootsplash. We want our command-line tools to STFU > if they don't have anything interesting to say. As a user, 99.99+% of > the time I don't care what grub or dmesg have to say. Agreed - the kernel should go out of the user's way if they want it to be silent. It's already possible, as long as KMS is not in use (since that automatically sets a mode and thus usually clears the screen). What you want is really the opposite of the kernel splash, or any splash on top of Linux (kernel or userspace) at all. Returning to cases where a splash running on Linux may be desired: I see adding to the initial logo as an interesting use case. An animation to show that the kernel hasn't crashed while booting is quite useful. Something like adding a spinning wheel underneath the initial logo helps. Macs do (or used to do) that after showing the apple, IIRC. I think this is where something simple and kernel based is helpful, vs. something userspace based. Maybe they can even build on top of each other, just like LILO used to print each letter as a confirmation of successfully executing a part of itself. Thinking of it: Loading a KMS driver basically always necessitates a mode change on variable resolution platforms such as PCs. And changing mode requires clearing the screen. Now, what if we could preload the new framebuffer with a splash, rather than a blank screen? That's not generally feasible (for example, double buffering is an implicit requirement), but who knows, maybe in the future. Just an odd idea. > Of course, with the kernel developer hat on, I want all of the clues > every time in case something goes wrong. But this shouldn't have to be > mutually exclusive. I agree - that's why it's important to be able to disable the bootsplash by changing the kernel cmdline. Max
next prev parent reply other threads:[~2018-01-03 17:38 UTC|newest] Thread overview: 193+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-13 19:47 [RFC PATCH v2 00/13] Kernel based bootsplash Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 01/13] bootsplash: Initial implementation showing black screen Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 23:55 ` Randy Dunlap 2017-12-13 23:55 ` Randy Dunlap 2017-12-14 15:37 ` Max Staudt 2017-12-14 15:37 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 02/13] bootsplash: Add file reading and picture rendering Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 21:35 ` Daniel Vetter 2017-12-13 21:35 ` Daniel Vetter 2017-12-13 21:35 ` Daniel Vetter 2017-12-14 15:36 ` Max Staudt 2017-12-14 15:36 ` Max Staudt 2017-12-14 15:36 ` Max Staudt 2017-12-19 12:23 ` Daniel Vetter 2017-12-19 12:23 ` Daniel Vetter 2017-12-19 12:23 ` Daniel Vetter 2017-12-19 13:34 ` Max Staudt 2017-12-19 13:34 ` Max Staudt 2017-12-19 13:34 ` Max Staudt 2017-12-19 13:57 ` Daniel Vetter 2017-12-19 13:57 ` Daniel Vetter 2017-12-19 14:07 ` Oliver Neukum 2017-12-19 14:07 ` Oliver Neukum 2017-12-31 12:53 ` Alan Cox 2017-12-31 12:53 ` Alan Cox 2017-12-31 12:53 ` Alan Cox 2018-01-03 18:04 ` Max Staudt 2018-01-03 18:04 ` Max Staudt 2018-01-03 18:04 ` Max Staudt 2017-12-19 15:41 ` Max Staudt 2017-12-19 15:41 ` Max Staudt 2017-12-19 15:41 ` Max Staudt 2017-12-19 16:02 ` Daniel Vetter 2017-12-19 16:02 ` Daniel Vetter 2017-12-19 16:02 ` Daniel Vetter 2017-12-19 16:23 ` Max Staudt 2017-12-19 16:23 ` Max Staudt 2017-12-19 16:23 ` Max Staudt 2017-12-20 9:45 ` Daniel Vetter 2017-12-20 9:45 ` Daniel Vetter 2017-12-20 9:45 ` Daniel Vetter 2017-12-19 16:09 ` Daniel Vetter 2017-12-19 16:09 ` Daniel Vetter 2017-12-19 16:09 ` Daniel Vetter 2017-12-19 16:26 ` Max Staudt 2017-12-19 16:26 ` Max Staudt 2017-12-19 16:26 ` Max Staudt 2017-12-19 21:01 ` Ray Strode 2017-12-19 21:01 ` Ray Strode 2017-12-19 21:01 ` Ray Strode 2017-12-20 13:14 ` Max Staudt 2017-12-20 13:14 ` Max Staudt 2017-12-20 13:14 ` Max Staudt 2017-12-20 15:35 ` Ray Strode 2017-12-20 15:35 ` Ray Strode 2017-12-20 15:35 ` Ray Strode 2017-12-20 16:52 ` Max Staudt 2017-12-20 16:52 ` Max Staudt 2017-12-20 16:52 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 04/13] bootsplash: Add corner positioning Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 05/13] bootsplash: Add animation support Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 06/13] vt: Redraw bootsplash fully on console_unblank Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 07/13] vt: Add keyboard hook to disable bootsplash Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 08/13] sysrq: Disable bootsplash on SAK Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 09/13] fbcon: Disable bootsplash on oops Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 10/13] Documentation: Add bootsplash main documentation Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 11/13] bootsplash: sysfs entries to load and unload files Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 12/13] tools/bootsplash: Add a basic splash file creation tool Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` [RFC PATCH v2 13/13] tools/bootsplash: Add script and data to create sample file Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:47 ` Max Staudt 2017-12-13 19:52 ` [RFC PATCH v2 00/13] Kernel based bootsplash Max Staudt 2017-12-13 19:52 ` Max Staudt 2017-12-13 19:52 ` Max Staudt 2017-12-19 16:16 ` Daniel Vetter 2017-12-19 16:16 ` Daniel Vetter 2017-12-19 16:16 ` Daniel Vetter 2017-12-19 17:04 ` Max Staudt 2017-12-19 17:04 ` Max Staudt 2017-12-19 17:04 ` Max Staudt 2017-12-19 17:26 ` Daniel Vetter 2017-12-19 17:26 ` Daniel Vetter 2017-12-19 17:26 ` Daniel Vetter 2017-12-19 18:40 ` Max Staudt 2017-12-19 18:40 ` Max Staudt 2017-12-19 18:40 ` Max Staudt 2017-12-20 9:43 ` Daniel Vetter 2017-12-20 9:43 ` Daniel Vetter 2017-12-20 9:43 ` Daniel Vetter 2017-12-20 10:06 ` Neil Armstrong 2017-12-20 10:06 ` Neil Armstrong 2017-12-20 10:06 ` Neil Armstrong 2017-12-20 10:14 ` Daniel Vetter 2017-12-20 10:14 ` Daniel Vetter 2017-12-20 10:14 ` Daniel Vetter 2017-12-20 14:55 ` Max Staudt 2017-12-20 14:55 ` Max Staudt 2017-12-20 15:11 ` Daniel Vetter 2017-12-20 15:11 ` Daniel Vetter 2017-12-20 15:11 ` Daniel Vetter 2017-12-20 15:19 ` Daniel Vetter 2017-12-20 15:19 ` Daniel Vetter 2017-12-20 15:19 ` Daniel Vetter 2017-12-20 15:22 ` Daniel Vetter 2017-12-20 15:22 ` Daniel Vetter 2017-12-20 15:22 ` Daniel Vetter 2017-12-20 16:23 ` Max Staudt 2017-12-20 16:23 ` Max Staudt 2017-12-20 16:23 ` Max Staudt 2017-12-20 16:15 ` Max Staudt 2017-12-20 16:15 ` Max Staudt 2017-12-20 16:15 ` Max Staudt 2017-12-31 12:44 ` Alan Cox 2017-12-31 12:44 ` Alan Cox 2017-12-31 12:44 ` Alan Cox 2018-01-03 18:00 ` Max Staudt 2018-01-03 18:00 ` Max Staudt 2017-12-20 14:16 ` Max Staudt 2017-12-20 14:16 ` Max Staudt 2017-12-20 14:16 ` Max Staudt 2017-12-20 14:10 ` Max Staudt 2017-12-20 14:10 ` Max Staudt 2017-12-20 14:10 ` Max Staudt 2017-12-31 12:35 ` Alan Cox 2017-12-31 12:35 ` Alan Cox 2017-12-31 12:35 ` Alan Cox 2018-01-03 17:56 ` Max Staudt 2018-01-03 17:56 ` Max Staudt 2018-01-03 17:56 ` Max Staudt 2017-12-19 20:30 ` Ray Strode 2017-12-19 20:30 ` Ray Strode 2017-12-19 20:30 ` Ray Strode 2017-12-20 13:03 ` Max Staudt 2017-12-20 13:03 ` Max Staudt 2017-12-20 13:03 ` Max Staudt 2017-12-20 15:21 ` Ray Strode 2017-12-20 15:21 ` Ray Strode 2017-12-20 15:21 ` Ray Strode 2017-12-20 16:44 ` Max Staudt 2017-12-20 16:44 ` Max Staudt 2017-12-20 16:44 ` Max Staudt 2017-12-21 14:51 ` Ray Strode 2017-12-21 14:51 ` Ray Strode 2017-12-21 14:51 ` Ray Strode 2017-12-21 16:32 ` Max Staudt 2017-12-21 16:32 ` Max Staudt 2017-12-20 11:08 ` Johannes Thumshirn 2017-12-20 11:08 ` Johannes Thumshirn 2017-12-20 11:22 ` Daniel Stone 2017-12-20 11:22 ` Daniel Stone 2017-12-20 11:22 ` Daniel Stone 2017-12-20 12:48 ` Johannes Thumshirn 2017-12-20 12:48 ` Johannes Thumshirn 2017-12-29 17:13 ` Jani Nikula 2017-12-29 17:13 ` Jani Nikula 2017-12-29 17:13 ` Jani Nikula 2018-01-03 17:38 ` Max Staudt [this message] 2018-01-03 17:38 ` Max Staudt 2017-12-21 9:48 ` Daniel Vetter 2017-12-21 9:48 ` Daniel Vetter 2017-12-21 9:48 ` Daniel Vetter 2017-12-21 16:52 ` Max Staudt 2017-12-21 16:52 ` Max Staudt 2017-12-21 16:52 ` Max Staudt 2017-12-21 15:00 ` Philip Müller 2017-12-21 15:00 ` Philip Müller
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=af4600fc-ad5d-411c-d899-9fe557a79add@suse.de \ --to=mstaudt@suse.de \ --cc=b.zolnierkie@samsung.com \ --cc=bernhard.rosenkranzer@linaro.org \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=jani.nikula@linux.intel.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michal@markovi.net \ --cc=oneukum@suse.com \ --cc=philm@manjaro.org \ --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: linkBe 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.