Summary: | GLX is missing Render sub-requests | ||
---|---|---|---|
Product: | XCB | Reporter: | Peter Harris <pharris> |
Component: | Protocol | Assignee: | Josh Triplett <josh> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | hto, jamey, jkolb |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Peter Harris
2007-11-07 11:04:00 UTC
We can add the Render and RenderLarge sub-encodings to the XML description of GLX without necessarily having them be used in the XCB C code generator. So this doesn't imply an ABI or API change, which is good. I believe this is actually a special case of a known general problem. Requests like PolyText8 and RenderCompositeGlyphs8, if they were fully described in the XML, can't generate correct code with our current code generator--and that's partly because we weren't sure what C API to give them. Once the Python code generator lands, it should be easy to at least make the code generator ignore unrepresentable descriptions, and at best generate a more friendly C API from them than the current byte-array interface. Assigning to Josh, though I'm sure he won't have time to work on this. Thomas and Jeremy seem more likely to make contributions here in the near future, so CC'ing them. :-) As an update, I've started using the GLX/Render definitions from the XML file in Mesa. It's probably easiest for XCB to just point at the Mesa repository, since they're more vested in keeping that file up to date. http://cgit.freedesktop.org/mesa/mesa/tree/src/mesa/glapi/gl_API.xml -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/proto/xcbproto/issues/7. |
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.