Summary: | [UXA] GLX_SGI_make_current_read missing from glx extension | ||
---|---|---|---|
Product: | Mesa | Reporter: | zhao jian <jian.j.zhao> |
Component: | Drivers/DRI/i965 | Assignee: | Eric Anholt <eric> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
xorg.conf
xorg.0.log glxinfo diffs between UXA and EXA |
Description
zhao jian
2008-12-22 19:22:51 UTC
Created attachment 21425 [details]
xorg.conf
Created attachment 21426 [details]
xorg.0.log
Created attachment 21427 [details]
glxinfo diffs between UXA and EXA
Not a release blocker. It still existed on gm45-32 with the following configuration: Kernel_version: 2.6.29-rc6 Libdrm: (master)2e2e8575b1ed4703653a72ac2b60b75316c388d7 Mesa: (mesa_7_4_branch)a8528a2e8653b5237c1d1d66fe98c6e031d007f9 Xserver: (server-1.6-branch)60c161545af80eb78eb790a05bde79409dfdf16e Xf86_video_intel: (2.7)238c2c40afd9f8b61479b8640d53f20d52fd7ddf It still existed with the newest code on gm45. commit fd4eed69e40cf090aa16e79a8596eb1442461829 Author: Eric Anholt <eric@anholt.net> Date: Thu Jul 2 15:24:54 2009 -0700 dri2: Enable GLX_SGI_make_current_read when the DRI driver supports it. This matches idr's 82f150d73cc9a7d8eaf7241a51b03af05bcec159 for DRI1. It should be noted the commit is on xserver master. (In reply to comment #8) > It should be noted the commit is on xserver master. Thanks Gordon. With the newest code, it now has GLX_SGI_make_current_read support now. Verified with: Libdrm:(master)72a29340ea3225550db6b009f4e50c77c7b1f394 Mesa:(master)862488075c5537b0613753b0d14c267527fc6199 Xserver:(master)fd4eed69e40cf090aa16e79a8596eb1442461829 Xf86_video_intel:(master)74227141923a2f5049592219ab80e8733062a5d9 Kernel: (drm-intel-next)1ae8c0a56eeb3ed358b78ccadd024d6b721f26bc |
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.