From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915: add basic pipe config dump support
Date: Tue, 28 May 2013 11:11:20 +0200 [thread overview]
Message-ID: <20130528091120.GT15743@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGRVyMjx3fFXuvsmCQwRKaqug6s6dXcse3SbN3rFiwN-dQ@mail.gmail.com>
On Mon, May 27, 2013 at 06:30:17PM -0300, Paulo Zanoni wrote:
> 2013/5/21 Daniel Vetter <daniel.vetter@ffwll.ch>:
> Besides this, I also booted a kernel with this patch, and on the first
> time we print these things, almost everything is zero, even stuff like
> pipe_bpp, even for enabled pipes. Is this expected?
Lack of hw state readout support for those. One of the goals of this is
that it's easier to see what pipe config the kernel is actually dealing
with, and knowing that we have no clue about the pipe bpp is useuful.
I'll respin the patch with your other comments fixed up.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-05-28 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 20:11 [PATCH] drm/i915: hw state readout&check support for cpu_transcoder Daniel Vetter
2013-05-10 8:02 ` Daniel Vetter
2013-05-21 22:50 ` [PATCH 1/3] " Daniel Vetter
2013-05-21 22:50 ` [PATCH 2/3] drm/i915: fixup i915_pipe_enabled check in i915_irq.c Daniel Vetter
2013-05-27 20:56 ` Paulo Zanoni
2013-05-21 22:50 ` [PATCH 3/3] drm/i915: add basic pipe config dump support Daniel Vetter
2013-05-27 21:30 ` Paulo Zanoni
2013-05-28 9:11 ` Daniel Vetter [this message]
2013-05-28 10:05 ` [PATCH] " Daniel Vetter
2013-05-28 14:17 ` Paulo Zanoni
2013-05-28 14:29 ` Daniel Vetter
2013-05-27 20:45 ` [PATCH 1/3] drm/i915: hw state readout&check support for cpu_transcoder Paulo Zanoni
2013-05-28 9:41 ` 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=20130528091120.GT15743@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.com \
/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