From: One Thousand Gnomes Subject: Re: [RFC] drm: add kernel-log renderer Date: Fri, 7 Mar 2014 21:58:08 +0000 Message-ID: <20140307215808.3755f855@alan.etchedpixels.co.uk> References: <1394131242-29567-1-git-send-email-dh.herrmann@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1394131242-29567-1-git-send-email-dh.herrmann@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: David Herrmann Cc: dri-devel@lists.freedesktop.org, Daniel Vetter , Dave Airlie , linux-kernel@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org > - 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