[ dri-Bugs-1681195 ] glDrawPixels fails with Tungsten 865G driver

Bugs item #1681195, was opened at 2007-03-15 07:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100387&aid=1681195&group_id=387 Please note that this message will contain a full copy of

[Bug 9599] i915 regression for 855gm in 6.5.2

http://bugs.freedesktop.org/show_bug.cgi?id=9599 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #1 from [EMA

[Bug 9264] GLX_BIND_TO_MIPMAP_TEXTURE_EXT attribute should only be GL_FALSE or GL_TRUE

http://bugs.freedesktop.org/show_bug.cgi?id=9264 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #1 from [EMA

[Bug 9200] mesa/progs/xdemos/glxpixmap error: GLXBadContext

http://bugs.freedesktop.org/show_bug.cgi?id=9200 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #13 from [EM

[Bug 8640] [i810] Driver does not support GLX_SGI_make_current_read

http://bugs.freedesktop.org/show_bug.cgi?id=8640 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #2 from [EMA

[Bug 8292] i915: texture crossbar

http://bugs.freedesktop.org/show_bug.cgi?id=8292 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #5 from [EMA

[Bug 8283] i915 can't swizzle TEX arguments

http://bugs.freedesktop.org/show_bug.cgi?id=8283 [EMAIL PROTECTED] changed: What|Removed |Added Priority|high|medium --- Comment #7 from [EMA

[Bug 9969] Heavy MGA DRI use causes Xorg lock

http://bugs.freedesktop.org/show_bug.cgi?id=9969 --- Comment #6 from [EMAIL PROTECTED] 2007-03-14 18:43 PST --- Prior to all last writed here log messages there was: Mar 15 04:42:38 mmx kernel: [drm:mga_dma_dispatch_vertex] vertex: buf=38 used=840 Mar 15 04:42:38 mmx kernel: [drm:mga

[Bug 9969] Heavy MGA DRI use causes Xorg lock

http://bugs.freedesktop.org/show_bug.cgi?id=9969 --- Comment #5 from [EMAIL PROTECTED] 2007-03-14 18:41 PST --- This how log was changed prior to that cicle. Mar 15 04:42:38 mmx kernel: [drm:drm_ioctl] pid=1135, cmd=0xc0286429, nr=0x29, dev 0xe200, auth=1 Mar 15 04:42:38 mmx kernel:

[Bug 9969] Heavy MGA DRI use causes Xorg lock

http://bugs.freedesktop.org/show_bug.cgi?id=9969 --- Comment #4 from [EMAIL PROTECTED] 2007-03-14 18:32 PST --- > What AGP mode are you using? I know that there are some buggy interactions between MGA and certain Via chipsets. Have you tried 1x? Moreover, i've tried next configurat

[Bug 9969] Heavy MGA DRI use causes Xorg lock

http://bugs.freedesktop.org/show_bug.cgi?id=9969 --- Comment #3 from [EMAIL PROTECTED] 2007-03-14 15:29 PST --- (In reply to comment #2) > Tried latest drm from freedesktop.org git reposotory and disabled preemption > in > kernel, still no results. What AGP mode are you using? I kn

[Bug 9969] Heavy MGA DRI use causes Xorg lock

http://bugs.freedesktop.org/show_bug.cgi?id=9969 --- Comment #2 from [EMAIL PROTECTED] 2007-03-14 15:06 PST --- Tried latest drm from freedesktop.org git reposotory and disabled preemption in kernel, still no results. P.S. Does someone read my messages or this bug list is dead? Serio

Testing the Radeon GART

Hi, Is there a simple way for me to test whether the GART is working on a radeon driver? I'm hacking the Radeon 200M, and I think that I've setup the GART properly. (unfortunately, the CP still doesn't work...) Is there a way for me to test if the memory is mapped in properly? Ideally, I woul

[Bug 9791] Glean case fragProg1 failure on 945g and 915gv

http://bugs.freedesktop.org/show_bug.cgi?id=9791 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|VERIFIED -- Configure bugmail: htt

[Bug 9686] google-earth cannot display map if zoom in on i945g

http://bugs.freedesktop.org/show_bug.cgi?id=9686 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|VERIFIED -- Configure bugmail: htt

[Bug 9379] drmCommandNone( fd, DRM_R128_CCE_IDLE ) - gives errno 22

http://bugs.freedesktop.org/show_bug.cgi?id=9379 --- Comment #6 from [EMAIL PROTECTED] 2007-03-14 00:27 PST --- I'm afraid the patch is not acceptable in this form. If anything, it should default to the span locking being enabled, with the possibility of disabling it via an environmen