From: Jocelyn Falempe <jfalempe@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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>,
John Ogness <john.ogness@linutronix.de>,
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>,
Jani Nikula <jani.nikula@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v9 0/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Date: Tue, 17 Dec 2024 15:46:12 +0100 [thread overview]
Message-ID: <301714d8-0723-4881-83e8-24523c121bfe@redhat.com> (raw)
In-Reply-To: <CAMuHMdU925NiJDy4fOcQhA=jp8=79rZ3h5-TYxCjzkGwqQdKOg@mail.gmail.com>
On 17/12/2024 15:19, Geert Uytterhoeven wrote:
> Hi Jocelyn,
>
> On Wed, Dec 4, 2024 at 6:41 PM 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.
>>
>> If you're curious on how it looks like, I've put a small demo here:
>> https://people.redhat.com/jfalempe/drm_log/drm_log_draft_boot_v2.mp4
>>
>> 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
>
> I gave this a try on Koelsch (R-Car M2-W), using rcar-du.
> Unfortunately I don't see any kernel messages, and my monitor complains
> about no signal. Does this require special support from the driver?
It doesn't require a special support from the driver. But as it is the
first drm client other than fbdev emulation, I'm not surprised it's
broken on some driver.
I know it works on virtio-gpu, nouveau, amdgpu, and even on a OnePlus 6
(Qualcomm SDM845/freedreno), without requiring driver changes.
Do you have a serial console on this device, to check if there is
something in kmsg?
Best regards,
--
Jocelyn
>
> CONFIG_DRM_CLIENT=y
> CONFIG_DRM_CLIENT_LIB=y
> CONFIG_DRM_CLIENT_SELECTION=y
> CONFIG_DRM_CLIENT_SETUP=y
> CONFIG_DRM_CLIENT_LOG=y
> # CONFIG_DRM_CLIENT_DEFAULT_FBDEV is not set
> CONFIG_DRM_CLIENT_DEFAULT_LOG=y
> CONFIG_DRM_CLIENT_DEFAULT="log"
>
> Switching to fbdev gives a working display, as before:
>
> CONFIG_DRM_CLIENT_DEFAULT_FBDEV=y
> # CONFIG_DRM_CLIENT_DEFAULT_LOG is not set
> CONFIG_DRM_CLIENT_DEFAULT="fbdev"
>
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2024-12-17 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:44 Jocelyn Falempe
2024-12-04 15:45 ` [PATCH v9 1/6] drm/panic: Move drawing functions to drm_draw Jocelyn Falempe
2024-12-11 21:34 ` [v9,1/6] " Kees Bakker
2024-12-12 8:36 ` Jocelyn Falempe
2024-12-04 15:45 ` [PATCH v9 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-12-05 16:21 ` Thomas Zimmermann
2024-12-12 7:41 ` Dan Carpenter
2024-12-12 8:49 ` Jocelyn Falempe
2024-12-12 8:53 ` Dan Carpenter
2024-12-12 10:07 ` Simona Vetter
2024-12-18 12:25 ` Markus Elfring
2024-12-04 15:45 ` [PATCH v9 3/6] drm/log: Do not draw if drm_master is taken Jocelyn Falempe
2024-12-04 15:45 ` [PATCH v9 4/6] drm/log: Color the timestamp, to improve readability Jocelyn Falempe
2024-12-04 15:45 ` [PATCH v9 5/6] drm/log: Implement suspend/resume Jocelyn Falempe
2024-12-04 15:45 ` [PATCH v9 6/6] drm/log: Add integer scaling support Jocelyn Falempe
2024-12-10 13:42 ` [PATCH v9 0/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen Jocelyn Falempe
2024-12-17 14:19 ` Geert Uytterhoeven
2024-12-17 14:46 ` Jocelyn Falempe [this message]
2024-12-17 14:54 ` Geert Uytterhoeven
2024-12-18 10:14 ` Jocelyn Falempe
2024-12-18 11:00 ` Geert Uytterhoeven
2024-12-18 11:41 ` Jocelyn Falempe
2024-12-18 14:18 ` Petr Mladek
2024-12-18 14:25 ` Geert Uytterhoeven
2024-12-18 14:58 ` Jocelyn Falempe
2024-12-18 15:03 ` Geert Uytterhoeven
2024-12-18 16:18 ` Petr Mladek
2024-12-19 11:24 ` 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=301714d8-0723-4881-83e8-24523c121bfe@redhat.com \
--to=jfalempe@redhat.com \
--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=geert@linux-m68k.org \
--cc=gpiccoli@igalia.com \
--cc=jani.nikula@linux.intel.com \
--cc=javierm@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®