From: Eric Anholt <eric@anholt.net>
To: Ben Widawsky <benjamin.widawsky@intel.com>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 5/5] intel/bdw: Update MI_BATCH_BUFFER_START for aub dumps
Date: Wed, 06 Nov 2013 15:04:45 -0800 [thread overview]
Message-ID: <87txfpdtde.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1383758132-28273-6-git-send-email-benjamin.widawsky@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 357 bytes --]
Ben Widawsky <benjamin.widawsky@intel.com> writes:
> From: Damien Lespiau <damien.lespiau@intel.com>
>
> The command now takes a 48bits address and is thus 1 byte longer.
I think you mean "1 dword"
Other than that, patches 2-5 are
Reviewed-by: Eric Anholt <eric@anholt.net>
(patch 1, I don't know anything about the set of PCI IDs so I've skipped
it).
[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2013-11-06 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 17:15 [PATCH 0/5] BDW libdrm support Ben Widawsky
2013-11-06 17:15 ` [PATCH 1/5] intel/bdw: Add broadwell chipset IDs Ben Widawsky
2013-11-06 17:15 ` [PATCH 2/5] intel/bdw: Handle gen8 bufmgr_init Ben Widawsky
2013-11-06 17:15 ` [PATCH 3/5] intel/bdw: Add gen8 to the decode init Ben Widawsky
2013-11-06 17:15 ` [PATCH 4/5] intel/bdw/aub: Update AUB trace block writes for 48-bit addressing Ben Widawsky
2013-11-06 17:15 ` [PATCH 5/5] intel/bdw: Update MI_BATCH_BUFFER_START for aub dumps Ben Widawsky
2013-11-06 23:04 ` Eric Anholt [this message]
2013-11-06 19:09 ` [PATCH 0/5] BDW libdrm support Kenneth Graunke
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=87txfpdtde.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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