http://bugs.freedesktop.org/show_bug.cgi?id=14696
--- Comment #2 from Shuang He <[EMAIL PROTECTED]> 2008-02-26 21:18:19 PST ---
Created an attachment (id=14610)
--> (http://bugs.freedesktop.org/attachment.cgi?id=14610)
xorg log
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.c
http://bugs.freedesktop.org/show_bug.cgi?id=14696
--- Comment #1 from Shuang He <[EMAIL PROTECTED]> 2008-02-26 21:17:19 PST ---
Created an attachment (id=14609)
--> (http://bugs.freedesktop.org/attachment.cgi?id=14609)
xorg conf
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.
http://bugs.freedesktop.org/show_bug.cgi?id=14696
Summary: [i965 Openarena] openarena performance drops by 22%
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Prio
Hi Thomas,
As i am in the process of cleaning up and making radeon
fence things bullet proof I am wondering what are the
difference btw fence flags and fence types ? Well i guess
the questions is more why fence flags are needed ?
My understanding is that fence_flags (DRM_FENCE_FLAG_EMIT,
DRM_FENC
http://bugs.freedesktop.org/show_bug.cgi?id=14695
Summary: Return type prototyped for irq_postinstall in FreeBSD
drmP.h is wrong
Product: DRI
Version: XOrg CVS
Platform: All
OS/Version: FreeBSD
Status: NEW
http://bugs.freedesktop.org/show_bug.cgi?id=14694
Summary: radeon_do_release prototyped twice in shared-
core/radeon_drv.h
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: FreeBSD
Status: NEW
Bugs item #1902526, was opened at 2008-02-26 21:58
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=1902526&group_id=387
Please note that this message will contain a full copy of
Here's a patch to fix the last issue that breaks DRI2 on i965. The
brw_context setup unconditionally references intel->front_region in
brw_FrameBufferTexInit. With DRI2 that region isn't valid and each
context may reference a different framebuffer, which can change over
time. Furthermore, the dr
Dave Airlie wrote:
>> Dave,
>> We've seen this on occasions before but never been able to track it
>> down, so if you
>> have a reliable way to reproduce it would be super.
>>
>> When drm_bo_mem_space() is called for a buffer, that buffer should no
>> longer be on the lru lists,
>> but it is obvi
> Dave,
> We've seen this on occasions before but never been able to track it
> down, so if you
> have a reliable way to reproduce it would be super.
>
> When drm_bo_mem_space() is called for a buffer, that buffer should no
> longer be on the lru lists,
> but it is obvious from the error messag
http://bugs.freedesktop.org/show_bug.cgi?id=14518
Michel Dänzer <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
Dave Airlie wrote:
> =
>
> [ INFO: possible recursive locking detected ]
>
> 2.6.24-0.123.rc6.fc9 #1
>
>
http://bugs.freedesktop.org/show_bug.cgi?id=14677
Summary: multi-texture not applied if blend is enabled
Product: Mesa
Version: CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority:
=
[ INFO: possible recursive locking detected ]
2.6.24-0.123.rc6.fc9 #1
-
14 matches
Mail list logo