Bug 26126 - [APPLE_object_purgeable] is not working with VBO
Summary: [APPLE_object_purgeable] is not working with VBO
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:07 UTC by Shuang He
Modified: 2010-06-07 18:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


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

Description Shuang He 2010-01-19 19:07:03 UTC
Created attachment 32733 [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_vertex_buffer_object. You could run and check attached piglit case for more details.
Comment 1 Chris Wilson 2010-03-05 03:23:08 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-06-07 18:14:57 UTC
Thanks, verified on G45 with:
Libdrm:		(master)2.4.20-20-g66375fd6e8d3e95df5d124883a1426460c1b8ed8
Mesa:		(master)mesa_7_6_1_rc1-8672-gb4483823d9c1205fb9ab8cf5b4c36ee610347a36
Xserver:		(master)xorg-server-1.8.0-361-gbc26665661565918af484ccd17caad951010df60
Xf86_video_intel:		(master)2.11.0-156-gd56ea7a852d7090360fe080acec268de55ee908d
Kernel:       (for-linus)c496fa1fff0248ef8cd637efb52b70dea7afaa9d


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.