On 12/13/2017 11:47 AM, Max Staudt wrote:
> This is the initial prototype for a lean Linux kernel bootsplash.
> 
> As it is now, it will show a black screen rather than a logo, and
> only if manually enabled via the kernel cmdline:
> 
>   bootsplash.enable=1

Is it .enable or .enabled?  (compare below)

> diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
> index 7f1f1fbcef9e..f3ff976266fe 100644
> --- a/drivers/video/console/Kconfig
> +++ b/drivers/video/console/Kconfig
> @@ -151,6 +151,30 @@ config FRAMEBUFFER_CONSOLE_ROTATION
>           such that other users of the framebuffer will remain normally
>           oriented.
>  
> +config BOOTSPLASH
> +     bool "Bootup splash screen"
> +     depends on FRAMEBUFFER_CONSOLE
> +     ---help---
> +       This option enables the Linux bootsplash screen.
> +
> +       The bootsplash is a full-screen logo or animation indicating a
> +       booting system. It replaces the classic scrolling text with a
> +       graphical alternative, similar to other systems.
> +
> +       Since this is technically implemented as a hook on top of fbcon,
> +       it can only work if the FRAMEBUFFER_CONSOLE is enabled and a
> +       framebuffer driver is active. Thus, to get a text-free boot,
> +       the system needs to boot with vesafb, efifb, or similar.
> +
> +       Once built into the kernel, the bootsplash needs to be enabled
> +       with bootsplash.enabled=1 and a splash file needs to be supplied.
               @@@@@@@@@@@@@@@@@@@@


-- 
~Randy
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Reply via email to