public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bxt: Add Broxton steppings
Date: Tue, 31 Mar 2015 14:56:14 +0200	[thread overview]
Message-ID: <20150331125614.GG6354@phenom.ffwll.local> (raw)
In-Reply-To: <1427801071.29759.0.camel@intel.com>

On Tue, Mar 31, 2015 at 02:24:31PM +0300, Imre Deak wrote:
> On pe, 2015-03-20 at 09:03 +0000, Nick Hoath wrote:
> > Signed-off-by: Nick Hoath <nicholas.hoath@intel.com>
> 
> Reviewed-by: Imre Deak <imre.deak@intel.com>

Applied to topic/bxt-stage1, thanks.
-Daniel

> 
> > ---
> >  drivers/gpu/drm/i915/i915_drv.h | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> > index eb38cd1..eec271a 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -2328,6 +2328,10 @@ struct drm_i915_cmd_table {
> >  #define SKL_REVID_D0		(0x3)
> >  #define SKL_REVID_E0		(0x4)
> >  
> > +#define BXT_REVID_A0		(0x0)
> > +#define BXT_REVID_B0		(0x3)
> > +#define BXT_REVID_C0		(0x6)
> > +
> >  /*
> >   * The genX designation typically refers to the render engine, so render
> >   * capability related checks should use IS_GEN, while display and other checks
> 
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-03-31 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  9:03 [PATCH] drm/i915/bxt: Add Broxton steppings Nick Hoath
2015-03-20 15:04 ` shuang.he
2015-03-31 11:24 ` Imre Deak
2015-03-31 12:56   ` 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=20150331125614.GG6354@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=imre.deak@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