From: John Ogness <john.ogness@linutronix.de>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
bluescreen_avenger@verizon.net,
Caleb Connolly <caleb.connolly@linaro.org>,
Petr Mladek <pmladek@suse.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Jocelyn Falempe <jfalempe@redhat.com>
Subject: Re: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Tue, 05 Nov 2024 14:22:29 +0106 [thread overview]
Message-ID: <84fro5es7m.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20241105125109.226866-3-jfalempe@redhat.com>
On 2024-11-05, Jocelyn Falempe <jfalempe@redhat.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@redhat.com>
Reviewed-by: John Ogness <john.ogness@linutronix.de> # console API
next prev parent reply other threads:[~2024-11-05 13:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 12:42 [PATCH v6 0/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 1/6] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-11-05 13:16 ` John Ogness [this message]
2024-11-06 0:38 ` kernel test robot
2024-11-06 1:30 ` kernel test robot
2024-11-05 12:42 ` [PATCH v6 3/6] drm/log: Do not draw if drm_master is taken Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 4/6] drm/log: Color the timestamp, to improve readability Jocelyn Falempe
2024-11-05 12:42 ` [PATCH v6 5/6] drm/log: Implement suspend/resume Jocelyn Falempe
2024-11-05 13:17 ` John Ogness
2024-11-05 15:08 ` Petr Mladek
2024-11-05 12:42 ` [PATCH v6 6/6] drm/log: Add integer scaling support Jocelyn Falempe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84fro5es7m.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=airlied@gmail.com \
--cc=bluescreen_avenger@verizon.net \
--cc=caleb.connolly@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gpiccoli@igalia.com \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pmladek@suse.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.