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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash Date: Sun, 31 Dec 2017 12:44:57 +0000 Message-ID: <20171231124457.12e954f8@alans-desktop> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from fuzix.org (www.llwyncelyn.cymru [82.70.14.225]) by gabe.freedesktop.org (Postfix) with ESMTPS id 48C5789C1C for ; Sun, 31 Dec 2017 12:45:07 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" 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==?= List-Id: dri-devel@lists.freedesktop.org PiBTbyBmdW5kYW1lbnRhbGx5IEkgZG9uJ3QgdGhpbmsgYW4gaW4ta2VybmVsIGJvb3RzcGxhc2gg aXMgYSBiYWQgaWRlYS4KPiBCdXQgbW9zdCBsaWtlbHkgeW91IHdhbnQgdGhpcyBvbiBhIGhpZ2hs eSBlbWJlZGRlZCBzeXN0ZW0sIHdoaWNoCgpJdCB3b3VsZG4ndCBiZSBpbiBrZXJuZWwgb24gc3Vj aCBhIGRldmljZSwgaXQnbGwgYmUgaW4gdGhlIGJvb3RzdHJhcApiZWZvcmUgKG9yIG9uIGEgZHVh bCBjb3JlIGRldmljZSBxdWl0ZSBwb3NzaWJseSB3aGlsZSkgdGhlIGtlcm5lbCBkYXRhIGlzCmJl aW5nIHVuY29tcHJlc3NlZC4gTW9zdCBkaXNwbGF5cyBuZWVkIHNvbWUgdGltZSB0byBzdGFiaWxp emUgY2xvY2tzIGFuZApQTExzIHNvIHlvdSBoYXZlIHRvIGdldCB0aGUgbW9kZSBzZXQgdXAgcmVh bGx5IHJlYWxseSBlYXJseSBvbiBlbWJlZGRlZApkZXZpY2VzIHdoZXJlIGluIHNvbWUgY2FzZXMg eW91J3ZlIGdvdCByZWd1bGF0b3J5IHJlcXVpcmVtZW50cyB0byBzaG93CnNvbWV0aGluZyBvbiB0 aGUgZGlzcGxheSByZWFsbHkgcmVhbGx5IHF1aWNrbHkuIENvbnN1bWVycyBwZXJjZWl2ZSBhCnNl Y29uZCBmcm9tIG9uIHRvIGRpc3BsYXlpbmcgc29tZXRoaW5nIGFzIHNsdWdnaXNoIG9uIGEgZml4 ZWQgZnVuY3Rpb24KZGV2aWNlLgoKPiBwcm9iYWJseSBpcyBjb21waWxlZCBmb3IgeW91ciBleGFj dCBodywgd2l0aCBwcmV0dHkgbXVjaCBldmVyeXRoaW5nCj4gYnVpbHQgaW4uIEFsc28sIG5vIGZi Y29uLCBtYXliZSBldmVuIG5vIHZ0IHN1YnN5c3RlbSBhdCBhbGwuCj4gRGVmaW5pdGVseSBub3Qg eW91ciBnZW5lcmFsIHB1cnBvc2UgZGlzdHJvLgoKUHJvYmFibHkgbm8gY29uc29sZSBvciB0dHkg bGF5ZXIgZXZlbiBwcmVzZW50LCBubyBrZXlib2FyZCBkcml2ZXJzLCBubwptb3VzZS4KCkFsYW4K X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751059AbdLaMp3 (ORCPT ); Sun, 31 Dec 2017 07:45:29 -0500 Received: from www.llwyncelyn.cymru ([82.70.14.225]:55568 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750762AbdLaMp2 (ORCPT ); Sun, 31 Dec 2017 07:45:28 -0500 Date: Sun, 31 Dec 2017 12:44:57 +0000 From: Alan Cox To: Daniel Vetter Cc: Max Staudt , Neil Armstrong , Bartlomiej Zolnierkiewicz , Linux Fbdev development list , michal@markovi.net, sndirsch@suse.com, Oliver Neukum , Takashi Iwai , dri-devel , Linux Kernel Mailing List , Bero =?UTF-8?B?Um9zZW5rcsOk?= =?UTF-8?B?bnplcg==?= , philm@manjaro.org Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash Message-ID: <20171231124457.12e954f8@alans-desktop> In-Reply-To: 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> Organization: Intel Corporation X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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