public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Nicolae Badiu <acavano@outlook.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: Access to B-spec for DevSNB
Date: Wed, 11 Jun 2014 13:07:04 +0300	[thread overview]
Message-ID: <20140611100704.GI27580@intel.com> (raw)
In-Reply-To: <BLU184-W95D370BC0C7B87EF6BA0B7A92B0@phx.gbl>

On Wed, Jun 11, 2014 at 06:52:15AM +0000, Nicolae Badiu wrote:
> Hey,
>  
> With regard to this commit: http://lists.freedesktop.org/archives/intel-gfx/2012-December/023210.html
>  
> How can I get access to this B-Spec document?

The public documents are here:
https://01.org/linuxgraphics/documentation/driver-documentation-prms

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-06-11 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  6:52 Access to B-spec for DevSNB Nicolae Badiu
2014-06-11 10:07 ` Ville Syrjälä [this message]
2014-06-11 10:22   ` Nicolae Badiu
2014-06-11 10:31 ` 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=20140611100704.GI27580@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=acavano@outlook.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