Bug 77822 - Implement real support for ARB_vertex_attrib_binding
Summary: Implement real support for ARB_vertex_attrib_binding
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium enhancement
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: i965-perf
  Show dependency treegraph
 
Reported: 2014-04-23 17:02 UTC by Kenneth Graunke
Modified: 2019-05-28 20:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Graunke 2014-04-23 17:02:01 UTC
We need to implement real ARB_vertex_attrib_binding support in i965.  Fredrik implemented the API front-end bits, and then code to translate the new data structures into the old gl_client_array structs as derived state.  Our driver still consumes the old structs.  Converting it to the new structs would eliminate the need to compute that derived state, and would also match the hardware better, cleaning up the drawing code.

This may entail rewriting parts of the VBO module, which could entail rewriting swtnl drivers...
Comment 1 Elizabeth 2017-10-27 21:59:20 UTC
Hello Kenneeth, any update on this? It is still valid? Otherwise closing soon. Thanks.
Comment 2 Matt Turner 2017-10-27 22:58:17 UTC
Yes. This is a developer's reminder to himself.
Comment 3 Kenneth Graunke 2017-10-27 23:05:56 UTC
We still need to do this someday.  Please don't close my bug.
Comment 4 Tapani Pälli 2019-05-28 10:02:20 UTC
Ken, is something still missing for 'real' ARB_vertex_attrib_binding support or can be resolve this one?
Comment 5 Kenneth Graunke 2019-05-28 20:58:06 UTC
Yeah.  Probably the closest step is this MR from Mathias: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/308


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.