From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Ivybridge is the odd one when it comes to pipe scalers
Date: Thu, 25 Apr 2013 16:32:55 +0200 [thread overview]
Message-ID: <20130425143255.GI6169@phenom.ffwll.local> (raw)
In-Reply-To: <1366899300-15352-1-git-send-email-damien.lespiau@intel.com>
On Thu, Apr 25, 2013 at 03:15:00PM +0100, Damien Lespiau wrote:
> Between ivb, hsw and vlv, only Ivybridge has sprites with scaling
> capabilities.
>
> Also make max_downscale coherent with that.
>
> v2: Rebase on top of the recent ivb/vlv/hsw sprite scaling fixes.
>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> (v1)
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-04-25 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 14:15 [PATCH] drm/i915: Ivybridge is the odd one when it comes to pipe scalers Damien Lespiau
2013-04-25 14:32 ` Daniel Vetter [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=20130425143255.GI6169@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.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