Re: [RFC PATCH 3/3] drm/log: Introduce a new boot logger to draw the kmsg on the screen

[Jocelyn Falempe]

On 05/09/2024 17:22, John Ogness wrote:
> On 2024-08-01, John Ogness <john.ogness@xxxxxxxxxxxxx> wrote:
> > On 2024-08-01, Jocelyn Falempe <jfalempe@xxxxxxxxxx> wrote:
> > > I think I can also register one console for each drm driver, which
> > > will simplify drm_log even further. (currently it would mean having a
> > > circular buffer and work function for each driver which is a bit too
> > > much).
> >
> > Indeed.
> >
> > > Do you know if there is a chance to have write_thread() in 6.12 or
> > > 6.13 ?
>
> FYI: The full NBCON API (with write_thread()) is now available in
> linux-next.
>
> It would be great to see a version of drm_log that only implements
> write_thread() and does not do any of its own buffering with workqueue
> and also does not need to track multiple graphic loggers at the same
> time.

Thanks for the head-up.
I will rebase it on top of Linux-next, and adapt to the new 
write_thread() API, it should be much simpler.


I also need to adapt to the drm client rework 
(https://patchwork.freedesktop.org/series/137391/) so that it will be 
possible to choose on kernel command line between drm_log and fbdev 
emulation/fbcon.

Best regards,

--

Jocelyn

> John Ogness