[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f50c7ba-f55a-30a4-6285-010a9d0e4dd2@suse.de>
Date: Wed, 3 Jan 2018 19:00:43 +0100
From: Max Staudt <mstaudt@...e.de>
To: Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Daniel Vetter <daniel@...ll.ch>
Cc: Neil Armstrong <narmstrong@...libre.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Linux Fbdev development list <linux-fbdev@...r.kernel.org>,
michal@...kovi.net, sndirsch@...e.com,
Oliver Neukum <oneukum@...e.com>,
Takashi Iwai <tiwai@...e.com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bero Rosenkränzer
<bernhard.rosenkranzer@...aro.org>, philm@...jaro.org
Subject: Re: [RFC PATCH v2 00/13] Kernel based bootsplash
On 12/31/2017 01:44 PM, Alan Cox wrote:
>> 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.
Oh no. Thanks for the input, that changes my perspective a bit.
So unless we could show it quickly enough, the kernel splash would be useful either as an addition on top of the bootloader's splash, or really aimed at fatter distros which wish to use something simple and kernel based.
Max
Powered by blists - more mailing lists