On Sat, 2004-03-06 at 04:31, SÃrgio Monteiro Basto wrote:
>
> On FooBillard-2.9 gives me a segment fault but at least doesn't hang my
> laptop.
No problems with foobillard here.
> configure foobillard-2.9 with --enable-debug:
>
> here is the results:
You need to get a stack trace with gdb or
On Sat, 03 Jan 2004, Andreas Stenglein wrote:
> here is what I fiddled together to support the 3rd TMU on radeon
> and 6TMUs on r200.
>
> I tried on R200 with multiarb.c and projtex.c and it works almost as it should.
> (projtex is broken somehow on r200, even with only 2 TMUs)
>
> ut2003_demo wo
On Sat, 2004-03-06 at 11:46, Michel Dänzer wrote:
> You need to get a stack trace with gdb or at least catchsegv.
Is this a stack trace ?
if I can do anything more? it will be a honor
thanks
--
Sérgio M. B.
#gdb foobillard
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)
Copyright 2003 Free Sof
Am Samstag, 6. März 2004 04:59 schrieb [EMAIL PROTECTED]:
> --- Additional Comments From [EMAIL PROTECTED] 2004-03-05 22:59
> --- Created an attachment (id=1130)
> --> (http://bugs.xfree86.org/attachment.cgi?id=1130&action=view)
> Enable 3D acceleration in XFree86-4.4.0
>
> I have manage
Am Samstag, 6. März 2004 04:11 schrieb Roland Scheidegger:
> I'm still trying to implement the glblendfuncseparate and
> glblendequationseparate (and fix glblendcolor) functions. Since I
> couldn't find a demo which tests these extensions, I figured I'd modify
> some demo, and this one,
> http://ww
On Sat, 2004-03-06 at 15:21, SÃrgio Monteiro Basto wrote:
> On Sat, 2004-03-06 at 11:46, Michel DÃnzer wrote:
> > You need to get a stack trace with gdb or at least catchsegv.
> Is this a stack trace ?
[...]
> Program received signal SIGFPE, Arithmetic exception.
> [Switching to Thread 16384 (LWP
On Sat, 2004-03-06 at 15:21, Michel Dänzer wrote:
> On Sat, 2004-03-06 at 15:21, Sérgio Monteiro Basto wrote:
> > On Sat, 2004-03-06 at 11:46, Michel Dänzer wrote:
> > > You need to get a stack trace with gdb or at least catchsegv.
> > Is this a stack trace ?
>
> [...]
>
> > Program received sign
Was the DRI tree ever synced with the XFree86 tree prior to 4.4.0? I
downloaded and installed 4.4.0 on a NetBSD system, thinking that MergedFB
would just work but, unfortunately, it doesn't.
Adam
---
This SF.Net email is sponsored by: IBM Li
On Sat, 2004-03-06 at 17:08, SÃrgio Monteiro Basto wrote:
> On Sat, 2004-03-06 at 15:21, Michel DÃnzer wrote:
> > On Sat, 2004-03-06 at 15:21, SÃrgio Monteiro Basto wrote:
> >
> > > Program received signal SIGFPE, Arithmetic exception.
> > > [Switching to Thread 16384 (LWP 28125)]
> > > 0x4075d064
--- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
>
> Was the DRI tree ever synced with the XFree86 tree prior to 4.4.0? I
> downloaded and installed 4.4.0 on a NetBSD system, thinking that
> MergedFB
> would just work but, unfortunately, it doesn't.
Nope, no mergedfb in 4.4. Mergedfb is only av
So I geuss the question should be:
What's the schedule for merging the DRI tree with the XFree86 tree and is
there any reason why this wasn't done before the release of 4.4.0?
Adam
On Sat, 6 Mar 2004, Alex Deucher wrote:
>
> --- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
> >
> > Was the DRI t
--- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
>
> So I geuss the question should be:
>
> What's the schedule for merging the DRI tree with the XFree86 tree
> and is
> there any reason why this wasn't done before the release of 4.4.0?
The trees were not merged more recently because the DRI was
On Sat, 6 Mar 2004, Alex Deucher wrote:
>
> --- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
> >
> > So I geuss the question should be:
> >
> > What's the schedule for merging the DRI tree with the XFree86 tree
> > and is
> > there any reason why this wasn't done before the release of 4.4.0?
>
> T
here is patch against Mesa CVS HEAD to refactor i830 texcombine
as its done in radeon/r200 driver.
it compiles, but its untested if it works.
feel free to test, modify, commit, drop
best regards,
Andreas Stenglein
Index: Mesa/src/mesa/drivers/dri/i830/i830_texstate.c
===
Am 2004.03.06 14:59:14 +0100 schrieb(en) Jaakko Niemi:
> On Sat, 03 Jan 2004, Andreas Stenglein wrote:
> > here is what I fiddled together to support the 3rd TMU on radeon
> > and 6TMUs on r200.
> >
> > I tried on R200 with multiarb.c and projtex.c and it works almost as it should.
> > (projtex is
On Sat, 2004-03-06 at 21:38, Andreas Stenglein wrote:
>
> I thought someone would do the conversion of the radeon/r200 driver
> from the t_dd_vbtmp.h template code to "t_vertex" [...]
I don't remember anyone saying they'd do it. Do you want to go for it?
:)
--
Earthling Michel DÃnzer |
What is the status of mach64 dri support on freebsd 5.2 ?
I tried to checkout from cvs and build the mach64-0-0-7, mach64-0-0-6,
and current mesa trees. mach64-0-0-7 builds, but does not support dri
on freebsd. mach64-0-0-6 seems to have the requisite code for
supporting dri on freebsd, but does
On Sat, 06 Mar 2004 20:16:38 +0100
Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Sat, 2004-03-06 at 17:08, Sérgio Monteiro Basto wrote:
[snip]
>
> [...]
>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40757507 in generic_interp (ctx=0x0, t=0.918080449, edst=96,
> > eout=21, ein=
On Sun, 7 Mar 2004 02:12:54 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Sat, 06 Mar 2004 20:16:38 +0100
> Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> > On Sat, 2004-03-06 at 17:08, Sérgio Monteiro Basto wrote:
> [snip]
> >
> > [...]
> >
> > > Program received signal SIGSEGV, Segmentati
> What is the status of mach64 dri support on freebsd 5.2 ?
nobody has tested it for a while, so I say it suffers from bitrot...
mach64-0-0-7 is the DRI branch to go with, and Mesa head, the code should
all be there, just needing some updates for FreeBSD 5.2,
I'll look into it over the next whi
20 matches
Mail list logo
