Am Samstag, 26. Oktober 2002 01:37 schrieb Keith Whitwell:
> Dieter Nützel wrote:
> > Am Freitag, 25. Oktober 2002 23:36 schrieb Dieter Nützel:
> >>Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
> >>>Charl P. Botha wrote:
> Dear list,
>
> This bug has so far been reproduced on
Dieter Nützel wrote:
Am Freitag, 25. Oktober 2002 23:36 schrieb Dieter Nützel:
Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
Charl P. Botha wrote:
Dear list,
This bug has so far been reproduced on my M7 (mobile 7500) laptop with
DRI CVS as well as on a TiBook (i.e. PPC) with 7500 (
Am Freitag, 25. Oktober 2002 23:36 schrieb Dieter Nützel:
> Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
> > Charl P. Botha wrote:
> > > Dear list,
> > >
> > > This bug has so far been reproduced on my M7 (mobile 7500) laptop with
> > > DRI CVS as well as on a TiBook (i.e. PPC) with 7500
On Fri, Oct 25, 2002 at 11:36:50PM +0200, Dieter Nützel wrote:
> TaskParallelism: r200_vtxfmt.c:925: r200FlushVertices: Assertion `vb.context
> == ctx' failed.
I think I have an idea about this, but I won't be able to try it out for a
bit. Doesn't radeonUnbindContext get called before radeonDes
Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
> Charl P. Botha wrote:
> > Dear list,
> >
> > This bug has so far been reproduced on my M7 (mobile 7500) laptop with
> > DRI CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks Wouter).
> >
> > Download http://cpbotha.net/thingies/glthread
Charl P. Botha wrote:
Dear list,
This bug has so far been reproduced on my M7 (mobile 7500) laptop with DRI
CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks Wouter).
Download http://cpbotha.net/thingies/glthreads.c and compile it with
something like:
gcc -I../include -O3 -ansi -pedantic -
I just tried this with RADEON_TCL_FORCE_DISABLE=1, RADEON_NO_VTXFMT=1 and
RADEON_NO_CODEGEN=1 and I can still reproduce the bug. Are any other bells
ringing?
No, now there's just hard work...
Keith
---
This sf.net email is sponsored by:
On Wed, Oct 23, 2002 at 07:56:28AM +0100, Keith Whitwell wrote:
> Ian Romanick wrote:
> >On Wed, Oct 23, 2002 at 12:27:57AM +0200, Charl P. Botha wrote:
> >
> >>On Tue, Oct 22, 2002 at 03:12:52PM -0700, Ian Romanick wrote:
> >>
> >>>On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:
>
Ian Romanick wrote:
On Wed, Oct 23, 2002 at 12:27:57AM +0200, Charl P. Botha wrote:
On Tue, Oct 22, 2002 at 03:12:52PM -0700, Ian Romanick wrote:
On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:
Run glthreads with something like: glthreads -n 5
Here's an additional data poi
On Wed, Oct 23, 2002 at 12:27:57AM +0200, Charl P. Botha wrote:
> On Tue, Oct 22, 2002 at 03:12:52PM -0700, Ian Romanick wrote:
> > On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:
> >
> > > Run glthreads with something like: glthreads -n 5
> >
> > Here's an additional data point.
On Tue, Oct 22, 2002 at 03:12:52PM -0700, Ian Romanick wrote:
> On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:
>
> > Run glthreads with something like: glthreads -n 5
>
> Here's an additional data point. If you move the call to glXDestroyContext
> to the end of draw_loop (and d
On Tue, Oct 22, 2002 at 12:46:27AM +0200, Charl P. Botha wrote:
> Run glthreads with something like: glthreads -n 5
Here's an additional data point. If you move the call to glXDestroyContext
to the end of draw_loop (and delete the other two calls), the program works
as expected on the Radeon.
12 matches
Mail list logo