From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Restore has_fbc=1 for ILK-M
Date: Tue, 6 Jun 2017 19:38:55 +0300 [thread overview]
Message-ID: <20170606163855.GF12629@intel.com> (raw)
In-Reply-To: <1496761903.2876.21.camel@rdvivi-vienna>
On Tue, Jun 06, 2017 at 03:11:32PM +0000, Vivi, Rodrigo wrote:
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks. Pushed to dinq.
>
> On Tue, 2017-06-06 at 16:32 +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Restore the lost has_fbc flag for mobile ILK.
> >
> > Cc: Carlos Santa <carlos.santa@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Fixes: a13233804686 ("drm/i915: Introduce GEN5_FEATURES for device info")
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_pci.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> > index cf43dc1d539f..f940e486a62a 100644
> > --- a/drivers/gpu/drm/i915/i915_pci.c
> > +++ b/drivers/gpu/drm/i915/i915_pci.c
> > @@ -208,7 +208,7 @@ static const struct intel_device_info intel_ironlake_d_info = {
> > static const struct intel_device_info intel_ironlake_m_info = {
> > GEN5_FEATURES,
> > .platform = INTEL_IRONLAKE,
> > - .is_mobile = 1,
> > + .is_mobile = 1, .has_fbc = 1,
> > };
> >
> > #define GEN6_FEATURES \
>
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-06 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 13:32 [PATCH] drm/i915: Restore has_fbc=1 for ILK-M ville.syrjala
2017-06-06 15:11 ` Vivi, Rodrigo
2017-06-06 16:38 ` 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=20170606163855.GF12629@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).