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, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: Jocelyn Falempe <jfalempe@redhat.com>
Subject: Re: [PATCH v3 2/4] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Thu, 12 Sep 2024 16:17:19 +0206 [thread overview]
Message-ID: <84cyl9c67s.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20240910070733.156127-3-jfalempe@redhat.com>
On 2024-09-10, 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.
> * drm_log can only be built-in (and drm must be built-in too).
> The reason is that, if you build it as a module, then a userspace
> application will be more appropriate than this module.
>
> 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-09-12 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 6:56 [PATCH v3 0/4] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-09-10 6:56 ` [PATCH v3 1/4] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-09-10 6:56 ` [PATCH v3 2/4] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-09-12 14:11 ` John Ogness [this message]
2024-09-10 6:56 ` [PATCH v3 3/4] drm/log: Do not draw if drm_master is taken Jocelyn Falempe
2024-09-10 6:56 ` [PATCH v3 4/4] drm/log: Color the timestamp, to improve readability Jocelyn Falempe
2024-10-04 22:40 ` [PATCH v3 0/4] drm/log: Introduce a new boot logger to draw the kmsg on the screen Caleb Connolly
2024-10-07 7:27 ` 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=84cyl9c67s.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=airlied@gmail.com \
--cc=bluescreen_avenger@verizon.net \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox