Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: No FBC on Cherry Trail ?
Date: Wed, 13 Dec 2017 18:53:25 +0200	[thread overview]
Message-ID: <20171213165325.GA10981@intel.com> (raw)
In-Reply-To: <103198ae-dc92-9445-8002-87d2a443cac3@redhat.com>

On Wed, Dec 13, 2017 at 05:45:01PM +0100, Hans de Goede wrote:
> Hi All,
> 
> intel_cherryview_info in drivers/gpu/drm/i915/i915_pci.c
> does not have has_fbc set. Is this an oversight / does
> the i915 code need work to allow FBC on CHT, or does CHT
> actually not have FBC?

The code is correct. No FBC on VLV/CHV.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-12-13 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 16:45 No FBC on Cherry Trail ? Hans de Goede
2017-12-13 16:53 ` Ville Syrjälä [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=20171213165325.GA10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=hdegoede@redhat.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