[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 9 Sep 2021 18:27:02 +0200
From: Noralf Trønnes <noralf@...nnes.org>
To: noralf@...nnes.org
Cc: airlied@...ux.ie, bp@...en8.de, dri-devel@...ts.freedesktop.org,
gregkh@...uxfoundation.org, hdegoede@...hat.com, hpa@...or.com,
javierm@...hat.com, linux-fbdev@...r.kernel.org,
linux-kernel@...r.kernel.org, maarten.lankhorst@...ux.intel.com,
mingo@...hat.com, mripard@...nel.org, pbrobinson@...il.com,
sam@...nborg.org, tglx@...utronix.de, tzimmermann@...e.de,
x86@...nel.org
Subject: Re: [RFC PATCH 0/4] Allow to use DRM fbdev emulation layer with
CONFIG_FB disabled
> > Hi Daniel,
> >
> > >
> > > I think for a substantial improvement here in robustness what you
really
> > > want is
> > > - kmscon in userspace
> > > - disable FB layer
> > > - ideally also disable console/vt layer in the kernel
> > > - have a minimal emergency/boot-up log thing in drm, patches for that
> > > floated around a few times
> >
> > I assume you refer to this work by David Herrmann:
> > "[RFC] drm: add kernel-log renderer"
> > https://lists.freedesktop.org/archives/dri-devel/2014-March/055136.html
> >
>
> There's also this:
>
> [PATCH v2 0/3] drm: Add panic handling
>
https://lore.kernel.org/dri-devel/20190311174218.51899-1-noralf@tronnes.org/
And here's a DRM console example that was part of the early drm_client work:
[RFC v4 25/25] drm/client: Hack: Add DRM VT console client
https://lore.kernel.org/dri-devel/20180414115318.14500-26-noralf@tronnes.org/
Noralf.
Powered by blists - more mailing lists