From: Keith Packard <keithp@keithp.com>
To: mesa-dev@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] Minor __DRIimage fixes for i965
Date: Fri, 22 Nov 2013 05:52:25 -0800 [thread overview]
Message-ID: <1385128347-17777-1-git-send-email-keithp@keithp.com> (raw)
While debugging the libdrm duplicate buffer object adventure, I managed to
temporarily understand object lifetimes in the __DRIimage getBuffers path, and
also to compare that to the DRI2 getBuffers path. Here are a couple of small
fixes.
I haven't looked at the i915 code, but I suspect the first one, and parts of
the second one would apply.
[PATCH 1/2] i965: Correct check for re-bound buffer in
The code was attempting to avoid re-creating the miptree when the loader
handed back the same bufffer we already had, but it was confused about how to
tell -- turns out the object actually shared between the loader and the driver
is the BO, not the region. And so, we compare BO pointers to see if the image
buffer needs to have a new miptree.
[PATCH 2/2] i965: Set fast color clear mcs_state on newly allocated
Here's a chunk of code that was just missing from the __DRIimage path as a
result of rebasing across some new driver additions.
Both of these fixes are candidates for 10.0 as they affect the __DRIimage
paths now used by Wayland.
-keith
next reply other threads:[~2013-11-22 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 13:52 Keith Packard [this message]
2013-11-22 13:52 ` [PATCH 1/2] i965: Correct check for re-bound buffer in intel_update_image_buffer Keith Packard
2013-11-22 13:52 ` [PATCH 2/2] i965: Set fast color clear mcs_state on newly allocated image miptrees Keith Packard
2013-11-25 20:48 ` Eric Anholt
2013-11-22 14:40 ` [PATCH 0/2] Minor __DRIimage fixes for i965 Paul Berry
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=1385128347-17777-1-git-send-email-keithp@keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mesa-dev@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