[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84fro5es7m.fsf@jogness.linutronix.de>
Date: Tue, 05 Nov 2024 14:22:29 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Jocelyn Falempe <jfalempe@...hat.com>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>, Javier Martinez Canillas
<javierm@...hat.com>, "Guilherme G . Piccoli" <gpiccoli@...lia.com>,
bluescreen_avenger@...izon.net, Caleb Connolly
<caleb.connolly@...aro.org>, Petr Mladek <pmladek@...e.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Cc: Jocelyn Falempe <jfalempe@...hat.com>
Subject: Re: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the
kmsg on the screen
On 2024-11-05, Jocelyn Falempe <jfalempe@...hat.com> wrote:
> drm_log is a simple logger that uses the drm_client API to print the
> kmsg boot log on the screen. This is not a full replacement to fbcon,
> as it will only print the kmsg. It will never handle user input, or a
> terminal because this is better done in userspace.
>
> Design decisions:
> * It uses the drm_client API, so it should work on all drm drivers
> from the start.
> * It doesn't scroll the message, that way it doesn't need to redraw
> the whole screen for each new message.
> It also means it doesn't have to keep drawn messages in memory, to
> redraw them when scrolling.
> * It uses the new non-blocking console API, so it should work well
> with PREEMPT_RT.
>
> This patch also adds a Kconfig menu to select the drm client to use.
> It can be overwritten on the kernel command line with:
> drm_client_lib.default=log or drm_client_lib.default=fbdev
>
> Signed-off-by: Jocelyn Falempe <jfalempe@...hat.com>
Reviewed-by: John Ogness <john.ogness@...utronix.de> # console API
Powered by blists - more mailing lists