From: Daniel Vetter <daniel@ffwll.ch>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915: Double wide pipe config
Date: Mon, 2 Sep 2013 20:53:01 +0200 [thread overview]
Message-ID: <20130902185301.GG9374@phenom.ffwll.local> (raw)
In-Reply-To: <1378146268-23306-1-git-send-email-ville.syrjala@linux.intel.com>
On Mon, Sep 02, 2013 at 09:24:23PM +0300, ville.syrjala@linux.intel.com wrote:
> I was suspecting double wide to be the cause of a bug report, and so
> started digging a bit. Sadly it looks like that bug is caused by something
> else, but I did end up fixing a double wide related bug anyway.
>
> The resulting series is here. It needs to be applied after the pipe config
> fixes seried I just posted since I'm using the new pipe_src_w in this
> series.
There's also the DOUBLE_WIDE check in intel_overlay I've hoped you'd
convert ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-09-02 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 18:24 [PATCH 0/5] drm/i915: Double wide pipe config ville.syrjala
2013-09-02 18:24 ` [PATCH 1/5] drm/i915: Move double wide mode handling into pipe_config ville.syrjala
2013-09-02 18:24 ` [PATCH 2/5] drm/i915: Add double_wide readout and checking ville.syrjala
2013-09-02 18:24 ` [PATCH 3/5] drm/i915: Check pixel clock limits on pre-gen4 ville.syrjala
2013-09-02 18:51 ` Daniel Vetter
2013-09-02 19:24 ` Ville Syrjälä
2013-09-03 7:55 ` Daniel Vetter
2013-09-02 18:24 ` [PATCH 4/5] drm/i915: pipe_src_w must be even in LVDS dual channel, DVO ganged, and double wide mode ville.syrjala
2013-09-02 18:24 ` [PATCH 5/5] drm/i915: Fix up pipe vs. double wide confusion ville.syrjala
2013-09-02 18:53 ` Daniel Vetter [this message]
2013-09-02 19:26 ` [PATCH 0/5] drm/i915: Double wide pipe config Ville Syrjälä
2013-09-02 19:31 ` [PATCH] drm/i915: Convert overlay double wide check over to " ville.syrjala
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=20130902185301.GG9374@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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