[Bug 13834] [i915 TTM 64-bit] Glean case blendFunc failed (sometimes hangs system)

2007-12-27 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13834 --- Comment #1 from [EMAIL PROTECTED] 2007-12-27 22:28 PST --- Created an attachment (id=13390) --> (http://bugs.freedesktop.org/attachment.cgi?id=13390&action=view) dmesg -- Configure bugmail: http://bugs.freedesktop.org/userprefs

[Bug 13834] New: [i915 TTM 64-bit] Glean case blendFunc failed (sometimes hangs system)

2007-12-27 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13834 Summary: [i915 TTM 64-bit] Glean case blendFunc failed (sometimes hangs system) Product: Mesa Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) S

Re: Buffer object access mode is per-operation, not per-buffer

2007-12-27 Thread Thomas Hellström
Keith Packard wrote: >I will not be able to comment on unreleased hardware designs and how >they affect the DRM design. Suffice it to say that this granularity of >signalling seems unnecessary to me; a single flush operation that was >signalled at the end of the sequence to free all of these buffe

Re: Buffer object access mode is per-operation, not per-buffer

2007-12-27 Thread Keith Packard
On Thu, 2007-12-27 at 10:34 +0100, Thomas Hellström wrote: > This would not be sufficient to optimize the (re-)use of buffers. Buffers are ready for re-use when they are no longer referenced by the command stream and when some kind of flush operation has occurred to remove them from caches or ot

[Bug 13656] glCompressedTexImage2DARB/glGetTexImage: texture format not set correctly

2007-12-27 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13656 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 13812] quake4 crash X

2007-12-27 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=13812 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Summar

Re: Buffer object access mode is per-operation, not per-buffer

2007-12-27 Thread Thomas Hellström
Keith Packard wrote: > >In particular, I think that adding what amounts to a state machine to >the fencing logic is a bad idea -- if the driver needs a state machine >to complete a particular fence, the driver should implement that state >machine internally. If the driver has no IRQs to drive that