From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752003AbdJYU1b (ORCPT <rfc822;w@1wt.eu>);
        Wed, 25 Oct 2017 16:27:31 -0400
Received: from mx2.suse.de ([195.135.220.15]:41763 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751900AbdJYU13 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 25 Oct 2017 16:27:29 -0400
Date: Wed, 25 Oct 2017 22:27:27 +0200
Message-ID: <s5hzi8fm0r4.wl-tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: <b.zolnierkie@samsung.com>, "Max Staudt" <mstaudt@suse.de>,
        <linux-fbdev@vger.kernel.org>, <michal@markovi.net>,
        "Michal Srb" <MSrb@suse.com>, "Oliver Neukum" <ONeukum@suse.com>,
        "Stefan Dirsch" <sndirsch@suse.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 08/14] bootsplash: Add file reading and picture rendering
In-Reply-To: <0b8c3644-1915-9a0a-696e-115742498cc2@infradead.org>
References: <20171025124602.28292-1-mstaudt@suse.de>
        <20171025124602.28292-9-mstaudt@suse.de>
        <0b8c3644-1915-9a0a-696e-115742498cc2@infradead.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 25 Oct 2017 19:32:53 +0200,
Randy Dunlap wrote:
> 
> On 10/25/17 05:45, Max Staudt wrote:
> 
> > diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
> > index a6617c07229a..c3496c5ac2bb 100644
> > --- a/drivers/video/console/Kconfig
> > +++ b/drivers/video/console/Kconfig
> > @@ -175,6 +175,14 @@ config BOOTSPLASH
> >            If unsure, say N.
> >            This is typically used by distributors and system integrators.
> >  
> > +config BOOTSPLASH_FILE
> > +        string "Default full path to bootsplash file"
> > +        depends on BOOTSPLASH
> > +        default "/bootsplash"
> > +        help
> > +          This file will be looked for in the initramfs and, if found, loaded
> > +          and used as a bootsplash.
> 
> 
> Some people try to avoid using initramfs.
> 
> Can one have a bootsplash without initramfs?

The current code is apparently not capable, but it shouldn't be too
difficult to re-use the built-in firmware.  i.e. essentially copying
fw_get_builtin_firmware() in drivers/base/firmware_class.c.

Also the bootsplash can appear after mounting the rootfs, too.  Before
that, it's simply a blank screen.  So it's not entirely useless even
without initrd / initramfs.


thanks,

Takashi