The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Dave Airlie <airlied@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] drm: add kernel-log renderer
Date: Fri, 7 Mar 2014 21:58:08 +0000	[thread overview]
Message-ID: <20140307215808.3755f855@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1394131242-29567-1-git-send-email-dh.herrmann@gmail.com>

>  - The renderer supports *any* RGB target, from 8bit to 32bit with
>    big-endian and little-endian support. The related pixel-renderer will
>    probably never win a beauty-contest, but it works.. Again, who cares
>    for debug-log rendering speed?

Debug log writing performance is extremely important when you are using
the log for debugging work rather than for panic display. I don't think
that is a show stopper because having a logger makes sense and someone
can write a better render engine if they care.

Supporting any target is also going to be useful but you do need to
support non linear framebuffers. A GMA500 with something like an X
display in use for example does not have a linear mapping of the
framebuffer memory. I don't believe its exactly unique in this.

What I am more dubious about is tying it to DRM. Yes it uses DRM
constants but it doesn't appear functionally to have a single tie to
either DRM or even framebuffer.

It's potentially useful in cases where neither framebuffer or DRM are
compiled into the system.

Alan

  parent reply	other threads:[~2014-03-07 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 18:40 [RFC] drm: add kernel-log renderer David Herrmann
2014-03-06 21:56 ` Bruno Prémont
2014-03-06 23:41   ` David Herrmann
2014-03-07  7:44     ` Bruno Prémont
2014-03-07  8:15       ` David Herrmann
2014-03-07 21:58 ` One Thousand Gnomes [this message]
2014-03-07 23:12   ` David Herrmann

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=20140307215808.3755f855@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.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