From: "Noralf Trønnes" <noralf@tronnes.org>
To: sam@ravnborg.org
Cc: airlied@linux.ie, bp@alien8.de, dri-devel@lists.freedesktop.org,
gregkh@linuxfoundation.org, hdegoede@redhat.com, hpa@zytor.com,
javierm@redhat.com, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mingo@redhat.com, mripard@kernel.org, pbrobinson@gmail.com,
tglx@linutronix.de, tzimmermann@suse.de, x86@kernel.org
Subject: Re: [RFC PATCH 0/4] Allow to use DRM fbdev emulation layer with CONFIG_FB disabled
Date: Thu, 9 Sep 2021 17:52:40 +0200 [thread overview]
Message-ID: <2527f0ef-dae1-9ad5-84a4-00712c44940d@tronnes.org> (raw)
In-Reply-To: <YS+Lhz9gg/0Caa+0@ravnborg.org>
> 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/
Noralf.
next parent reply other threads:[~2021-09-09 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YS+Lhz9gg/0Caa+0@ravnborg.org>
2021-09-09 15:52 ` Noralf Trønnes [this message]
2021-09-09 16:27 ` [RFC PATCH 0/4] Allow to use DRM fbdev emulation layer with CONFIG_FB disabled Noralf Trønnes
2021-08-27 10:00 Javier Martinez Canillas
2021-08-27 17:50 ` Thomas Zimmermann
2021-08-27 20:20 ` Daniel Vetter
2021-08-27 22:02 ` Javier Martinez Canillas
2021-08-31 12:35 ` Daniel Vetter
2021-09-01 9:08 ` Javier Martinez Canillas
2021-09-02 14:31 ` Daniel Vetter
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=2527f0ef-dae1-9ad5-84a4-00712c44940d@tronnes.org \
--to=noralf@tronnes.org \
--cc=airlied@linux.ie \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=pbrobinson@gmail.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=tzimmermann@suse.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).