From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Date: Sun, 31 Dec 2017 12:44:57 +0000 Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash Message-Id: <20171231124457.12e954f8@alans-desktop> List-Id: References: <20171213194755.3409-1-mstaudt@suse.de> <20171219161630.GI26573@phenom.ffwll.local> <2f8a1a08-911d-a511-2968-4d89418ac212@suse.de> <573d4050-7607-b8e4-7552-83966f551ba3@suse.de> <20171220094355.GJ26573@phenom.ffwll.local> <20171220101421.GM26573@phenom.ffwll.local> <5dc7f218-9113-fad3-c0a8-883c4bae4e02@suse.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Daniel Vetter Cc: Linux Fbdev development list , Oliver Neukum , michal@markovi.net, Bartlomiej Zolnierkiewicz , sndirsch@suse.com, Neil Armstrong , Takashi Iwai , dri-devel , Linux Kernel Mailing List , Max Staudt , philm@manjaro.org, Bero =?UTF-8?B?Um9zZW5rcsOk?= =?UTF-8?B?bnplcg==?= > So fundamentally I don't think an in-kernel bootsplash is a bad idea. > But most likely you want this on a highly embedded system, which It wouldn't be in kernel on such a device, it'll be in the bootstrap before (or on a dual core device quite possibly while) the kernel data is being uncompressed. Most displays need some time to stabilize clocks and PLLs so you have to get the mode set up really really early on embedded devices where in some cases you've got regulatory requirements to show something on the display really really quickly. Consumers perceive a second from on to displaying something as sluggish on a fixed function device. > probably is compiled for your exact hw, with pretty much everything > built in. Also, no fbcon, maybe even no vt subsystem at all. > Definitely not your general purpose distro. Probably no console or tty layer even present, no keyboard drivers, no mouse. Alan