Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4669
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2498
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4908
--- Additional Comments From [EMAIL PROTECTED] 2005-10-27 22:19 ---
Same
On Fri, 2005-10-28 at 14:13 +1000, Benjamin Herrenschmidt wrote:
> This is exactly the kind of crap I see here too on the G5, so that irons
> out a 32 vs 64 bits issue.
>
> The strangest thing is that paulus is currently running a version of the
> driver on his G5 that does not have this issue. I
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4908
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2498
[EMAIL PROTECTED] changed:
What|Removed |Added
--
On Thu, 2005-10-27 at 14:00 +0200, Mattias Nissler wrote:
> Any ideas what could be causing those problems? Is quake3 rendering
> correctly on x86 at the moment? I am willing to look into the source
> if someone could give me a few hints what to look for. I can also do
> some further testing
Am Donnerstag, den 27.10.2005, 19:27 -0400 schrieb Adam K Kirchhoff:
> FYI, doom3 seems to run with the latest r300 drivers. It's slow, and
> there are definite texture problems (lots of flickering), but it doesn't
> crash. You can see a screenshot at http://68.44.156.246/doom3.png
I'm not sure
Hello DRI testers,
I finally got around to bringing the snapshot build up to speed with the
latest changes in the build process and uploaded a first set of new
snapshots to http://dri.freedesktop.org/snapshots/. They are completely
untested so be prepared for problems with the first couple of roun
FYI, doom3 seems to run with the latest r300 drivers. It's slow, and
there are definite texture problems (lots of flickering), but it doesn't
crash. You can see a screenshot at http://68.44.156.246/doom3.png
It looks washed out because I had to increase the brightness in gimp to
make anyth
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4908
--- Additional Comments From [EMAIL PROTECTED] 2005-10-27 16:05 ---
Creat
Mesa Tests R300 driver latest cvs!
Remove the Warn_once from results
Xorg Options
#Option GARTSise "32"
#Option "RenderAccel" "true"
#Tiling disable
SUCESS
./arbvptest1
./arbvptest3
./arbvptorus
./arbvpwarpmesh
./arbfptest1
./arbfpspec
./arbfptexture
./blendminmax
./blendsquare
./bufferobj
./bug
It's a just a simple txt pointing out some warnings that i have during
compilation. They should be easy to resolve...
Please check this warning!!
Compiler gcc 3.4.4, glibc 2.3.5
Easy Solution, just give new line. Don't know if it's possible to give new
line. Special file...:(
PATH= Mesa/src/me
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3715
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3613
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4908
Summary: [Intel / i830] drmAddMap(backbuffer) failed
Product: DR
On 10/27/05, Aapo Tahkola <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Oct 2005 15:03:26 +0200
> Jerome Glisse <[EMAIL PROTECTED]> wrote:
>
> > On 10/27/05, Aapo Tahkola <[EMAIL PROTECTED]> wrote:
> > > On Thu, 27 Oct 2005 14:00:18 +0200
> > > Mattias Nissler <[EMAIL PROTECTED]> wrote:
> > >
> > > > 3.
On Thu, 27 Oct 2005 15:03:26 +0200
Jerome Glisse <[EMAIL PROTECTED]> wrote:
> On 10/27/05, Aapo Tahkola <[EMAIL PROTECTED]> wrote:
> > On Thu, 27 Oct 2005 14:00:18 +0200
> > Mattias Nissler <[EMAIL PROTECTED]> wrote:
> >
> > > 3. quake3: I did some heavy struggling with the quake3 source tree,
> >
On 10/27/05, Aapo Tahkola <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Oct 2005 14:00:18 +0200
> Mattias Nissler <[EMAIL PROTECTED]> wrote:
>
> > 3. quake3: I did some heavy struggling with the quake3 source tree,
> > but now I could get it running. It renders correctly when I use the
> > Mesa software
Mattias Nissler wrote:
Any ideas what could be causing those problems? Is quake3 rendering
correctly on x86 at the moment?
Yes, I just played it for a while on Sunday, with the latest and
greatest in CVS at the time.
Adam
---
This
On Thu, 27 Oct 2005 14:00:18 +0200
Mattias Nissler <[EMAIL PROTECTED]> wrote:
> 3. quake3: I did some heavy struggling with the quake3 source tree,
> but now I could get it running. It renders correctly when I use the
> Mesa software renderer (but unplayable then, of course). With r300 I
> m
Hi guys,
my congratulations for the r300 driver work. I tested a recent CVS
version here on my G4 Powerbook and it really rocks. Finally I got 3D
support, thank you. Here is my experience with some apps:
1. ppracer: Works quite well. I only found one level with rendering
bugs, but after t
Don't bother to aplly it, i already seen what happened. My mistake..
---
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End
On Thu, 27 Oct 2005 00:23:54 +0100
"pedro.lixo" <[EMAIL PROTECTED]> wrote:
> Just to warn that in last commit to r300, aapot has forgeted to del the 2
> headers that have been deleted from the project both #include "r200_tcl.h",
> #include "r200_sanity.h", are not needed anymore, so please updat
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4901
--- Additional Comments From [EMAIL PROTECTED] 2005-10-27 01:09 ---
Same
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4901
Summary: Radeon seccolor broken for tcl_mode=1
Product: Mesa
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4900
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4900
Summary: Radeon LINEAR and EXP fogging don't work in non-fogcoord
28 matches
Mail list logo