http://bugs.freedesktop.org/show_bug.cgi?id=14507
--- Comment #9 from Michael Fu <[EMAIL PROTECTED]> 2008-02-16 18:08:52 PST ---
I'm not familiar with how fedora build package, but would you be able to just
pull the source code from repository and build , just for verification.
--
Configur
http://bugs.freedesktop.org/show_bug.cgi?id=14340
--- Comment #13 from Diego <[EMAIL PROTECTED]> 2008-02-16 12:09:17 PST ---
So, after changing the suggested line, and connecting gdb this is where gdb
stops:
Program received signal SIGABRT, Aborted.
0xb7f32410 in __kernel_vsyscall ()
(gdb) b
http://bugs.freedesktop.org/show_bug.cgi?id=13915
--- Comment #3 from Brian Paul <[EMAIL PROTECTED]> 2008-02-16 08:58:31 PST ---
I've fixed the issue in sw/xlib Mesa too (master and 7.0 branch).
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are recei
http://bugs.freedesktop.org/show_bug.cgi?id=14507
--- Comment #8 from Alexey Kuznetsov <[EMAIL PROTECTED]> 2008-02-16 06:47:10
PST ---
https://admin.fedoraproject.org/pkgdb/packages/name/xorg-x11-drv-i810
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- Yo
http://bugs.freedesktop.org/show_bug.cgi?id=14507
--- Comment #7 from Alexey Kuznetsov <[EMAIL PROTECTED]> 2008-02-16 06:46:56
PST ---
That version not yet in Fedora development build, i expect several problems to
build driver. Please provide detailed instructions for fedora distrib, thanks.
On Fri, 15 Feb 2008 09:57:32 -0500, "=?UTF-8?Q?Kristian_H=C3=B8gsberg?=" wrote:
> Last night I committed the DRI2 work that I've been sitting on for
> quite a while now.
Congratulations!
> - only intel hardware, limited testing on i965 and up. Gotta
> reinstall that box...
Is that "you've only
http://bugs.freedesktop.org/show_bug.cgi?id=13980
Roland Scheidegger <[EMAIL PROTECTED]> changed:
What|Removed |Added
Attachment #13627|0 |1
is obso
http://bugs.freedesktop.org/show_bug.cgi?id=13918
--- Comment #5 from Thomas Hellström <[EMAIL PROTECTED]> 2008-02-16 01:46:29
PST ---
(In reply to comment #4)
> Yeah, this has always been a problem, but things seem to have become more
> fragile since TTM. We should fix the fence wait code