Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/sprite: Always enable the scaler on IronLake
Date: Mon, 16 Apr 2012 08:54:17 -0700	[thread overview]
Message-ID: <20120416085417.3b652e43@jbarnes-desktop> (raw)
In-Reply-To: <1334589278_8242@CP5-2952>

On Mon, 16 Apr 2012 16:14:25 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Mon, 16 Apr 2012 08:00:17 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Funky... do you notice any difference in output (fuzziness or anything)
> > with the scaler enabled?  Wonder if it's safe to enable for 1:1 scaling
> > on SNB as well.
> 
> Hard to tell. Without the scaler being enabled, it is black. :)

Oh I misread "doesn't update" as "you only see the first frame".  I
guess we can compare on SNB at least and potentially enable the scaler
all the time.

> The content I was using was regular compressed mpeg-ts, so not the best
> for juding aesthetic quality. We'd have to render some test geometry,
> such as testdisplay to be sure. (testplanes? ;)

There's a sprite_on test in there somewhere, but a new testplanes
wouldn't hurt.

> The docs do suggest that we disable the scaler to save power, so
> probably best if we keep the code as is.

Ok, sounds good.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2012-04-16 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 21:14 [PATCH] drm/i915/sprite: Always enable the scaler on IronLake Chris Wilson
2012-04-16 15:00 ` Jesse Barnes
2012-04-16 15:14   ` Chris Wilson
2012-04-16 15:54     ` Jesse Barnes [this message]
2012-04-16 17:01   ` 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=20120416085417.3b652e43@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chris@chris-wilson.co.uk \
    --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