All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Noralf Trønnes" <noralf@tronnes.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: Fri, 10 Sep 2021 18:05:58 +0200	[thread overview]
Message-ID: <YTuCZjdV1tH5+tB/@ravnborg.org> (raw)
In-Reply-To: <ff6a590e-19ee-b2b6-bed5-236962637418@tronnes.org>

Hi Noralf,

On Thu, Sep 09, 2021 at 06:27:02PM +0200, Noralf Trønnes wrote:
> 
> > > 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/

Thanks for providing these pointers. Looks forwards to find time to play
with all this. Having an embedded board without any fbdev stuff seems
like a nice goal.

	Sam

      reply	other threads:[~2021-09-10 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 10:00 [RFC PATCH 0/4] Allow to use DRM fbdev emulation layer with CONFIG_FB disabled Javier Martinez Canillas
2021-08-27 10:00 ` [RFC PATCH 1/4] fbdev: Rename fb_*_device() functions names to match what they do Javier Martinez Canillas
2021-08-27 17:50 ` [RFC PATCH 0/4] Allow to use DRM fbdev emulation layer with CONFIG_FB disabled 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
2021-09-01 14:17         ` Sam Ravnborg
2021-09-09 15:52           ` Noralf Trønnes
2021-09-09 16:27             ` Noralf Trønnes
2021-09-10 16:05               ` Sam Ravnborg [this message]

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=YTuCZjdV1tH5+tB/@ravnborg.org \
    --to=sam@ravnborg.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=noralf@tronnes.org \
    --cc=pbrobinson@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.