From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754528AbdKIMkV (ORCPT ); Thu, 9 Nov 2017 07:40:21 -0500 Received: from mx2.suse.de ([195.135.220.15]:53635 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754499AbdKIMkU (ORCPT ); Thu, 9 Nov 2017 07:40:20 -0500 Message-ID: <1510230976.2975.10.camel@suse.com> Subject: Re: [RFC 00/14] Kernel based bootsplash From: Oliver Neukum To: Pavel Machek , Max Staudt Cc: michal@markovi.net, b.zolnierkie@samsung.com, Michal Srb , Stefan Dirsch , Takashi Iwai , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 09 Nov 2017 13:36:16 +0100 In-Reply-To: <20171109115655.GA18436@atrey.karlin.mff.cuni.cz> References: <20171025124602.28292-1-mstaudt@suse.de> <20171109115655.GA18436@atrey.karlin.mff.cuni.cz> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Donnerstag, den 09.11.2017, 12:56 +0100 schrieb Pavel Machek: > > "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). Hi, well you are not required to use a boot splash. Though I note that many people want a boot splash. However, if you use a boot splash at all, you will not see the messages, so how does it matter to you if it comes out of the initrd? And of course we want a reliable boot, but that is an orthogonal issue. And this solution is more reliable than plymouth. Regards Oliver