[Bug 15203] r300 lockup

2008-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=15203 --- Comment #28 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-02 01:48:07 PST --- (In reply to comment #27) > I would rather we just disable the writeback than adding some work around[...] Disabling writeback is just a workaround... -- C

[Bug 15203] r300 lockup

2008-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=15203 --- Comment #29 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-02 02:14:48 PST --- I think the best intermediate solution would be to increase the timeout. In the long run, the error should be propagated and handled properly everywhere. The l

[Bug 15203] r300 lockup

2008-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=15203 --- Comment #30 from Markus Amsler <[EMAIL PROTECTED]> 2008-04-02 03:34:50 PST --- Created an attachment (id=15627) --> (http://bugs.freedesktop.org/attachment.cgi?id=15627) Wait forever fix Currently I have this patch in my tree. It's no i

Re: Gallium: Fix for tgsi_emit_sse2()

2008-04-02 Thread Stephane Marchesin
So, we should really fix this. The two options are : - Keep a different calling convention under linux (cdecl by default, which requires saving esi by hand in the shader) and apply Victor's patch which saves & restores this register - Use the same calling convention on all platforms, that is change

Re: Gallium: Fix for tgsi_emit_sse2()

2008-04-02 Thread Keith Whitwell
Sorry, this slipped through the net a little... Given how much is hardcoded with rtasm, I'd prefer to use a single calling convention everywhere, whether that's STDCALL or CDECL or something else I don't mind. Probably STDCALL because some compilers are too dumb to use anything else?? In wh

[Bug 15203] r300 lockup

2008-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=15203 --- Comment #31 from Markus Amsler <[EMAIL PROTECTED]> 2008-04-02 06:01:37 PST --- Created an attachment (id=15628) --> (http://bugs.freedesktop.org/attachment.cgi?id=15628) Handle error in BEGIN_RING macro Is this an acceptable patch? Retu

Re: DRI2 direct rendering

2008-04-02 Thread Steven J Newbury
> On Tue, 2008-04-01 at 20:50 +0800, Kristian Høgsberg wrote: > > On Tue, Apr 1, 2008 at 5:25 AM, Jin, Gordon <[EMAIL PROTECTED]> > > wrote: > > > Kristian H?gsberg wrote on Tuesday, April 01, 2008 5:35 AM: > > > > > > > > > > Hi, > > > > > > > > I just committed the last big chunk of DRI2 work,

Re: DRI2 direct rendering

2008-04-02 Thread Steven J Newbury
On Wed, 2008-04-02 at 15:43 +0100, Steven J Newbury wrote: > > On Tue, 2008-04-01 at 20:50 +0800, Kristian Høgsberg wrote: > > > On Tue, Apr 1, 2008 at 5:25 AM, Jin, Gordon <[EMAIL PROTECTED]> > > > wrote: > > > > Kristian H?gsberg wrote on Tuesday, April 01, 2008 5:35 AM: > > > > > > > > > > > > >

[Bug 15330] New: DRI is not working with 945GME

2008-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=15330 Summary: DRI is not working with 945GME Product: DRI Version: DRI CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium

Another question about DRI2 direct rendering

2008-04-02 Thread Marco
I tried the latest drm,mesa e xorg from git to test the new DRI2 direct rendering and possibly AIGLX. I also pull the latest intel batchbuffer branch to have DRI2 enabled. These are my logs: 1) It seems (from Xorg.log) that direct rendering is enabled with DRI2; 2) The output of glxinfo keeps sayi