Bug 26127 - [APPLE_object_purgeable] is not working with PBO
Summary: [APPLE_object_purgeable] is not working with PBO
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 19:09 UTC by Shuang He
Modified: 2010-03-10 18:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
piglit case (9.78 KB, text/plain)
2010-01-19 19:09 UTC, Shuang He
Details

Description Shuang He 2010-01-19 19:09:13 UTC
Created attachment 32734 [details]
piglit case

System Environment:
--------------------------
mesa (object-purgeable)a5a74202661423326184151e6ba746c3b4564186
(git://people.freedesktop.org/~ickle/mesa)
Libdrm:         (master)db50f5127421ac8f4e3ce4eb7c27d27475781488
Xserver:               
(server-1.7-branch)aea5ace1ee331fab0b72885ce0d5d3fc235e0708
Xf86_video_intel:              
(master)8ecf70ea553083cbc26928dc3973c8f6f8b3d9d0



Bug detailed description:
-------------------------
I'm testing this extension on my G41.
this extension seems not working with GL_ARB_pixel_buffer_object. You could
run and check attached piglit case for more details.
Comment 1 Chris Wilson 2010-03-05 03:23:03 UTC
Ah, I used the wrong buffer lookup function which was returning the currently bound target as opposed to the named buffer.
s/get_buffer/_mesa_buffer_lookup/
Comment 2 Shuang He 2010-03-10 18:20:26 UTC
Thanks, verified against:
Libdrm:         (master)04fd3872ee8bd8d5e2c27740508c67c2d51dbc11
Mesa:           (master)6f4ce4a4fed9f0f0f0ee89a63e406ab86dae7150
Xserver:                (master)bbae92795c7eab062e6722c42fa7915e0cee5d69
Xf86_video_intel:               (master)318aa9ed799197810e2039dbe3ec51559dcc888c
Kernel:       (drm-intel-next)338d762fc2dc2c1493813123fc4cea998bb3e683


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.