Hi,
I got software fallbacks to work with Savage IX ;-), more or less. It's
scribbling all over the screen, and what it draws depends on the
background. Furthermore, the way it scribbles stuff over the screen
depends on whether I have DisableTile set to true of false. Looks like
frame buffer
On Fri, 16 Jan 2004 01:59:16 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Fri, 2004-01-16 at 01:10, Alex Deucher wrote:
nevermind... I think I figured it out... I had to re-run 'make World'.
still shouldn't 'make Makefiles' have worked too?
World does a lot more than that, but you
Hi,
I just plugged the Savage4 into my box and gave it a go. I'm trying to
give a complete summary of what I noticed so far. First a few notes
about the card and my setup:
The card has only one DVI port, no VGA. I assume that this port outputs
analog and digital signals. However, I can only test
On Fri, 16 Jan 2004 20:00:59 +0100
Roland Scheidegger [EMAIL PROTECTED] wrote:
ok, here's another attempt, which uses an external dxtn library (patch
against current Mesa cvs trunk).
There is a new configuration option to enable the s3tc extension even if
the external library is not
On Fri, 16 Jan 2004 17:43:42 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Fri, 2004-01-16 at 17:09, Felix Kühling wrote:
On Fri, 16 Jan 2004 01:59:16 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
[snip]
PS: Please, guys, trim the superfluous citations from your posts...
I didn't
On Thu, 15 Jan 2004 01:02:48 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-01-14 at 23:38, Felix Kühling wrote:
On Wed, 14 Jan 2004 03:12:37 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-01-14 at 01:47, Felix Kühling wrote:
It makes sense since
What you're describing is the typical symptoms of a chip lockup. I
havn't got one of those in a while on my ProSavage. Jesse, are you using
the latest CVS for both the 2D and 3D driver?
Marco, I'm going to start looking into 3D on Savage IX on the weekend.
Regards,
Felix
On Wed, 14 Jan 2004
Good to know. Another file I found useful is in the UtahGLX driver:
utah/glx-xf4/servGL/hwglx/s3savage/savage_hw.h
It's probably more focused on 3D.
/Felix
On Thu, 15 Jan 2004 10:57:27 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I was just looking through the original savage code drop
Thanks for your explanation. I think I'm beginning to understand. To get
this straight, access to the frame buffer by the 2D engine, 3D engine
and the CPU all go through bitmap descriptors which can translated
from/to tiled/linear adresses. The format is somehow specified by the
tiled surface
Assuming you appended hw/savage to SUBDIRS in lib/XvMC/Imakefile I
attached the lib/XvMC/hw/savage/Imakefile that I used and a small patch
that fixes a few include file problems. I hope that does the trick.
Felix
On Thu, 15 Jan 2004 11:57:10 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
On Thu, 15 Jan 2004 01:02:48 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-01-14 at 23:38, Felix Kühling wrote:
On Wed, 14 Jan 2004 03:12:37 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-01-14 at 01:47, Felix Kühling wrote:
It makes sense since the color
Alex,
honestly I don't understand much of what you were writing about tiling
registers, PBDs, GBDs and so on. I don't have much experience with low
level aspects of graphics engines. The last one I programmed on the
register level was an original VGA under DOS many years ago. ;-) I'm a
bit
On Wed, 14 Jan 2004 03:12:37 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-01-14 at 01:47, Felix Kühling wrote:
The funny thing is, that I'm seeing the same on Radeon (r100). It took
me a while to realize that this was the behaviour you were describing
;-). I always thought
On Mon, 12 Jan 2004 18:17:15 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I just fixed 3D at 32 bpp on savage4 and commited the changes. It
ended up being a define with the wrong bits set. I get between 280 and
300 fps in glxgears on savage4 at 32 bpp and around 600 at 16 bpp.
textures
On Tue, 13 Jan 2004 14:38:37 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2004-01-12 at 17:44, Michel Dänzer wrote:
There are still minor problems, e.g. in the xscreensaver endgame hack,
but those might be related to colour material (known to horribly break
trackballs, e.g.).
Hi Alex,
I just got your cards. :) I'll try to get a Savage branch up and running
on my home computer as soon as possible. It may take until the weekend,
though. I'm pretty busy.
Some more comments inline ...
On Tue, 13 Jan 2004 09:58:48 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
---
On Tue, 13 Jan 2004 21:12:53 +0100
Roland Scheidegger [EMAIL PROTECTED] wrote:
Michel Dänzer wrote:
On Tue, 2004-01-13 at 14:51, Felix Kühling wrote:
On Tue, 13 Jan 2004 14:38:37 +0100
Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2004-01-12 at 17:44, Michel Dänzer wrote
On Mon, 12 Jan 2004 07:54:35 -0700
Brian Paul [EMAIL PROTECTED] wrote:
Hmmm, I don't remember how to do this and I can't seem to find the CVS
command for setting permissions. Anyone?
-Brian
IIRC the only way is to set the permissions of the RCS file directly in
the repository. Meta data
On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
whoops. I'll have to check that out. Can you point me to the code?
I'm assuming savage_span in the DRI somewhere? Also, only 16 bpp works
at the moment on savage4. I've only been able to run one 3d app at 32
On Sun, 11 Jan 2004 12:54:31 +0100
Andreas Stenglein [EMAIL PROTECTED] wrote:
will the savage driver work with savage4 pci cards?
greetings,
Andreas
It should, though I think you'd be the first one to test it on a PCI
card. PCI support is currently disabled with 2.6 kernel. Your best bet
is
On Sun, 11 Jan 2004 09:31:05 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
whoops. I'll have to check that out. Can you point me to the
code?
I'm
on the idea of Felix Kühling that the order in which state atoms
are emitted might be important on the radeon, I thought maybe it might
be important on the r200 as well, even though there are no lockups.
With the attached patch indeed the random color flashings seem to be
gone (at least
On Thu, 8 Jan 2004 15:40:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
well, I managed to fix the 2D corruption in tile mode on savage4. the
problem is that the bits of the GBD (MM816C) have different meaning on
savage4 vs. twister/prosavage. The fix is to use the
I tested your patch on my ProSavage. It works and it speeds up glxgears
by over 50fps. I was surprised to read numbers over 500fps on Savage4 as
that's about what I'm getting with ProSavage too. It used to be about
490, with your patch it's about 550 now.
BTW, I just saw your other mail about the
On Wed, 7 Jan 2004 14:56:24 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
just as a follow up, I got the DRM to build under 2.4.24, (redhat uses
2.6 MM in rh9). Unfortunately, I can't get pcmcia to work for me in
2.4.24, so I can either hack on the savage driver or have network
access,
On Wed, 7 Jan 2004 07:47:08 +0100
Dieter Nützel [EMAIL PROTECTED] wrote:
SuSE 9.0
Yast2 wouldn't start the YOU online update subthread anylonger.
SunWave1 /home/nuetzel# Fatal error in __driConfigOptions line 63, column 0:
illegal default value: 1.0.
/sbin/yast2: line 184: 26298
On Wed, 07 Jan 2004 08:01:54 -0700
Brian Paul [EMAIL PROTECTED] wrote:
The Mesa 5.1 release seems to have been fairly solid so I'm planning
on releasing Mesa 6.0 (stabilized release advertising OpenGL 1.5
support) pretty soon.
So, if anyone has any bug fixes or changes, get them in
2.4.24 is probably rather too new than too old. I compiled the DRM
successfully on 2.4.21. See the workaround that I added for 2.6 kernels.
It disables the driver-specific ioctls completely as I didn't want to
bother figuring out a real solution at that time, knowing that the DRM
driver would be
Pavel,
after reading your patch more carfully I decided to write the number
parsing functions myself. No offense, but your version does not parse
numbers in scientific notation like 1.5e-8, it is not good enough at
detecting errors in the input and in some cases it is even wrong. I
tested my
On Sun, 4 Jan 2004 14:50:34 +0100
Andreas Stenglein [EMAIL PROTECTED] wrote:
Am 2004.01.03 16:22:54 +0100 schrieb(en) Felix Kühling:
[...]
I just added a short HOWTO to the Wiki:
http://dri.sourceforge.net/cgi-bin/moin.cgi/ConfigurationForDevelopers.
Let me know if you find any
On Sun, 04 Jan 2004 20:08:12 +1030
Rick Harris [EMAIL PROTECTED] wrote:
Hi all,
Am wondering what stage DRI support for the S3 Savage IX/MV cards is at
(if any).
Is there any work being currently done on the 3D driver for this card ?
Alex Deucher and I will start working on Savage IX/MV
On Sat, 03 Jan 2004 22:27:53 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
[snip]
I tested these patches on a Radeon 7500 with flightgear, torcs, tuxracer
(and glxgears ;-) without noticing any problems. I can't test on R200
(yet). My CPU doesn't have a SSE unit, so
.: The driconf patches seem to be against the wrong tree. I had to
apply the *_context.c parts manually.
On Sun, 4 Jan 2004 14:50:34 +0100
Andreas Stenglein [EMAIL PROTECTED] wrote:
Am 2004.01.03 16:22:54 +0100 schrieb(en) Felix Kühling:
[...]
I just added a short HOWTO to the Wiki:
http
On Sat, 3 Jan 2004 00:30:35 +0100
Andreas Stenglein [EMAIL PROTECTED] 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
On Sat, 03 Jan 2004 22:06:27 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
I was wondering why flightgear was so slow so I did some profiling and
debugging. And I found out that apperently the entire vtxfmt code path
is not working. I believe the root cause
Hi,
I believe I got it right this time. :) I attached three small patches
that re-enabled the vtxfmt paths in the radeon and r200 drivers. One is
for _tnl_Begin to call the driver's NotifyBegin callback again.
Alternatively, if the drivers are supposed to work correctly without
this callback,
Hi,
this is referring to the a very reproducable lockup that occurred with
glaxium on r100 hardware. Several months ago I tracked it down to
emission of state changes and introduced a workaround that waits for 3D
idle before state changes. Now I had a new idea about a possible cause
of trouble:
On Thu, 01 Jan 2004 02:01:27 +
Alan Cox [EMAIL PROTECTED] wrote:
I played tuxracer using XFree 4.3.0 and my test code last might. Depth
buffering in some cases is shot, there is a lot of fallback stuff
occuring for clipped polygons that isnt working and things are a
peculiar brown colour
+0100
Felix Kühling [EMAIL PROTECTED] wrote:
On Wed, 31 Dec 2003 00:00:17 +0100
Jacek Pop [EMAIL PROTECTED] wrote:
On Tue, Dec 30, 2003 at 09:38:21PM +0100, Felix Kühling wrote:
And I found out that apperently the entire vtxfmt code path is not working.
Was it working before newmesa
On Wed, 31 Dec 2003 00:00:17 +0100
Jacek Pop [EMAIL PROTECTED] wrote:
On Tue, Dec 30, 2003 at 09:38:21PM +0100, Felix Kühling wrote:
And I found out that apperently the entire vtxfmt code path is not working.
Was it working before newmesa?
I'm not sure. Looking at an old config-0-0-1
Hi,
I was wondering why flightgear was so slow so I did some profiling and
debugging. And I found out that apperently the entire vtxfmt code path
is not working. I believe the root cause is that radeonNotifyBegin is
never called with current Mesa. So the driver's own vtxfmt functions are
never
Hi,
I fixed two TCL bugs on radeon that appeared after the move to
Mesa-newtree. A patch is attached.
The light_model_cntl thing looks almost like a copy-paste from R200.
This fixes missing colors and textures in various applications (pulsar,
queens, endgame, tuxkart, torcs, ...).
Here is the patch. :)
On Fri, 26 Dec 2003 19:44:50 +0100
Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I fixed two TCL bugs on radeon that appeared after the move to
Mesa-newtree. A patch is attached.
The light_model_cntl thing looks almost like a copy-paste from R200.
This fixes missing
On Tue, 23 Dec 2003 11:17:20 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Mon, 22 Dec 2003 15:30:47 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I'd be willing to help on the 2D side, I just need to get ahold of
an
old
On Mon, 22 Dec 2003 15:30:47 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I'd be willing to help on the 2D side, I just need to get ahold of an
old savage board to test with. I have an old laptop with a savage ix
in it, but it's be in the process of being sold, so I doubt I'll be
able
On Mon, 22 Dec 2003 15:30:47 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I'd be willing to help on the 2D side, I just need to get ahold of an
old savage board to test with. I have an old laptop with a savage ix
in it, but it's be in the process of being sold, so I doubt I'll be
able
On Sun, 21 Dec 2003 10:41:24 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
[snip]
My first approach was to restore the old primitive after each clipped
one. But that would result in reduntant primitive switching if several
primitives are clipped in a row. Therefore I
On Mon, 22 Dec 2003 11:59:34 -0800
Tim Roberts [EMAIL PROTECTED] wrote:
On Sun, 21 Dec 2003 16:35:01 +0100, Felix K_hling wrote:
as mentioned earlier on [EMAIL PROTECTED] I'm working on the savage S3
code drop, specifically on the 3D driver. A few days ago I managed to
get a working 3D
PM 20/12/2003, Felix Kühling wrote:
We had a similar problem with the 2D driver on the savage-1_0_0-branch.
Accelerated stuff worked just fine for me but direct frame buffer access
was broken. It turned out to be quite simple to fix. However, this fix
didn't work for Maximo, so I suspect
On Sun, 21 Dec 2003 08:35:14 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
I recompiled a static Xserver so that could get a backtrace inside the
driver. This is the result:
Program received signal SIGSEGV, Segmentation fault.
0x080532e3 in SavageHelpSolidROP
On Sun, 21 Dec 2003 09:52:32 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Keith Whitwell wrote:
Felix Kühling wrote:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems
Hello Tim,
as mentioned earlier on [EMAIL PROTECTED] I'm working on the savage S3
code drop, specifically on the 3D driver. A few days ago I managed to
get a working 3D driver ported to Mesa 4. It is now in DRI CVS on the
savage-2-0-0-branch. However, many users (including myself) are
I believe this is also missing in the MGA driver. The symptoms can be
seen for instance in the gflux demo. Part of the waving square is not
drawn.
Regards,
Felix
On Sat, 20 Dec 2003 04:44:31 -0800
Felix Kuehling [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both started
since I use different hardware primitives
On Sat, 20 Dec 2003 09:08:50 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
as I recall the savage hardware needs a tiled framebuffer for the 3d
engine, but 2d engine can use linear or tile. Most drivers use linear,
so that's probably what the savage driver did originally, now that it
has
Pablo,
I see exactly the same problem that you describe. I just didn't look
into it because it doesn't really bother me. I use 1024x768 in X and
also on the text console via vesafb because screen stretching looks
really ugly.
We should probably get in touch with Tim Roberts who maintains the
I'm confused ...
I solved my other kernel include file problems and now I get exactly the
same error as you. I don't understand how I was ever able to compile
this. :-/ Probably an older libc version that I used two months ago had
different kernel include files. Now I can't find e.g.
On Fri, 19 Dec 2003 06:26:26 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
perhaps some sort of conflict with the local header file? I recall
seeing a version of videodev.h in the 2d driver directory in cvs, but I
haven't really looked into it.
Ah, thanks for the pointer. There is
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both started
since I use different hardware primitives for quads and
triangles/polygons.
TAG(quad) in t_dd_tritmp.h calls RASTERIZE( GL_TRIANGLES ) directly
before
On Thu, 18 Dec 2003 09:02:44 +0100
Mario Premke [EMAIL PROTECTED] wrote:
Hello,
the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show
'Indirect Rendering' any more, but starting q3demo or a
3D screensaver the X-Server crashes and restarts, is that what is meant by: '
On Thu, 18 Dec 2003 10:40:55 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
Felix,
I tested your driver on my savage4 and i couldn't make the 3D
driver work (i changed the code to enable direct render on savage4), the
Xfree86 just can't find /dev/dri/cardX and i loaded agpgart and
On Thu, 18 Dec 2003 14:30:21 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
At 12:38 PM 18/12/2003, Felix Kühling wrote:
The device node is created by XFree86 when it looks for the DRM. Make
sure that the directory /dev/dri exists and that the Xserver has
permission to create new device nodes
On Wed, 17 Dec 2003 09:06:52 +0100
Mario Premke [EMAIL PROTECTED] wrote:
Hello list,
I made a CVS checkout and edited the host.def like it is described in the
Compilation Guide. Now I get a compilation error - apparently because of
combining the '-c' and '-o' compiler flags, what seems
Hi savage users,
I finally managed to port the savage 3D driver to the Mesa version in
DRI CVS. I just committed it to the savage-2-0-0-branch. Testers are
welcome. I am aware that there are still several problems with the
driver but I havn't seen anything so far that didn't occur with the
] Error 2
Thanks
Mario
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Felix
Kühling
Gesendet: Mittwoch, 17. Dezember 2003 09:21
An: Mario Premke
Cc: dri-devel
Betreff: Re: [Dri-devel] Compilation Error
On Wed, 17 Dec 2003
On Wed, 17 Dec 2003 13:51:47 +0100
Mario Premke [EMAIL PROTECTED] wrote:
Thanks for the quick response!
And [Ooopps], you were right - I messed up my host.def. I did a new check out and
only commented out PPC, Alpha and added '#define
MesaUse3DNow YES' and it compiles [so far].
BTW, how
On Wed, 17 Dec 2003 10:50:26 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
Felix,
Very nice. I'll try it latter. What version of Xfree86 did you
test it?
The one on the savage-2-0-0-branch. The XFree86 version that is
installed by my distribution is 4.2.1. But that shouldn't matter
On Wed, 17 Dec 2003 05:51:43 -0800
Felix Kuehling [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/dri
Module name: xc
Repository: xc/xc/lib/GL/mesa/src/drv/savage/
Changes by: [EMAIL PROTECTED] 03/12/17 05:51:43
Log message:
Fix line pitch in span functions.
Forgot to mention
On Wed, 17 Dec 2003 09:36:16 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
Felix,
I realize you are focusing on the 3D side, but I noticed that the HW
XvMC stuff isn't in cvs. I would assume that should pretty much just
drop into place once the mesa port is done? No sense in
On Sun, 14 Dec 2003 15:11:06 +0100
Dieter Nützel [EMAIL PROTECTED] wrote:
Am Samstag, 13. Dezember 2003 23:43 schrieb Felix Kühling:
Hi,
after Dieter's last mail I wonder why the environment variable
R200_NO_TCL was revived. I didn't notice this before so I assume this
slipped
Hi,
after Dieter's last mail I wonder why the environment variable
R200_NO_TCL was revived. I didn't notice this before so I assume this
slipped in during the move to Mesa CVS. Since environment variables can
be used to override configuration options this is really no longer
necessary. You can
59 FPS sounds like it's synchronizing with your monitor refresh rate. I
don't understand why that's happening, though, and why it depends on the
color depth. You can try playing with some environment variables. They
differ depending on whether you use XFree86 CVS or DRI CVS:
XFree86 CVS: (only
Hi,
I attached a patch that eliminates the dependency of xmlconfig.o on the
symbol __driConfigOptions in the DRI drivers. Keith, how do you like it?
I wasn't aware that I do need Mesa CVS write access for changes in the
DRI drivers before now. :-/ Brian, could you give me CVS write access
On Wed, 10 Dec 2003 09:26:59 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
I briefly tried the DRI trunk after the newmesa merge last night. In
flightgear with TCL enabled the old lighting problem seems to be back.
Everything is too dark, but banking to one
Steve,
There are lots of things to be done with the savage driver. At the
moment I can hardly make the time to port it to current Mesa and the
recent change to Mesa 5.0.2 won't exactly speed this up. Here is a list
of the most important issues on the TODO list (in arbitrary order) for
the savage
Hi all,
There is now a new set of trunk snapshots available at
http://dri.freedesktop.org/~fxkuehl/snapshots that was built after the
newmesa merge. Unfortunately I didn't manage to set up the a cron-job
for the build yet.
Regards,
Felix
On Thu, 11 Dec 2003 08:59:54 -0800
Felix Kuehling
Hi,
I briefly tried the DRI trunk after the newmesa merge last night. In
flightgear with TCL enabled the old lighting problem seems to be back.
Everything is too dark, but banking to one side makes things brighter.
There is another problem with Torcs that looks like texture coordinates
are
On Tue, 09 Dec 2003 22:50:54 -0800
Eric Anholt [EMAIL PROTECTED] wrote:
[snip]
P.S. Felix, I still have testing that r128 diff on my TODO, sorry for
not trying it yet.
No problem. It's not really a priority and nothing else depends on it. I
was just starting to forget about it myself, so I
On Tue, 09 Dec 2003 17:53:14 -0600
David D. Hagood [EMAIL PROTECTED] wrote:
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a
On Tue, 9 Dec 2003 15:11:06 +
Alan Hourihane [EMAIL PROTECTED] wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
Hi,
I tried to compile the new dri trunk on freedesktop.org now. I checked
out Mesa-newtree and set the MesaSrcDir correctly in host.def and ran
make World. These are the last few lines of make output:
gcc-3.3 -c -O2 -gstabs+ -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes
On Tue, 9 Dec 2003 22:39:15 +
Alan Hourihane [EMAIL PROTECTED] wrote:
This sounds to me like you are picking up a stale copy of glcore.h from
somewhere.
There shouldn't be a xc/lib/GL/include/GL/internal/glcore.h any more,
it'll use the one from Mesanew in
Am 08.12.2003 18:57:14 schrieb(en) Ian Romanick:
Keith Whitwell wrote:
Keith Whitwell wrote:
Is there any reason why these things are extern references rather than
parameters to an initialization function?
Basically by making them extern references, it means that the files
cannot
Am 08.12.2003 22:41:40 schrieb(en) Felix Kühling:
Am 08.12.2003 18:57:14 schrieb(en) Ian Romanick:
[snip]
Felix would be able to answer better, but I believe the reason was so
that the config utility could load the *_dri.so and get the list of
options for that driver.
Precisely. I
Hi,
as I'm trying to port the savage driver I stumbled over this. The mga
and r128 drivers define different values for DEPTH_SCALE in xxx_tris.c.
This is a parameter of t_dd_tritmp.h and specifies the minimum
resolvable unit of depth coordinates for computing polygon offsets. In
mgatris.c it is
On Tue, 2 Dec 2003 10:38:33 +
Alan Hourihane [EMAIL PROTECTED] wrote:
I need some entries for the XFree86 changelog to say what changed
over the DRI since 4.3.0.
Rather than me troll the CVS lists, I thought I'd post here to get a
few words for each entry.
The CHANGELOG entries
On Mon, 01 Dec 2003 09:11:07 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
Felix,
Not yet. Hang on a bit longer. I'm quite busy with university stuff
right now, but I'm confident that a first 3D driver for current mesa
will be available before Christmas.
I'm really busy too, have you
On Thu, 27 Nov 2003 22:23:23 +0100
Felix Kühling [EMAIL PROTECTED] wrote:
[snip]
Using gcc-2.95.4 makes the snapshots a lot smaller due to different
debug info. The build system also has a gcc-3.3 installed. I'll look
into the configuration file patching necessary for that. There should
also
On Fri, 28 Nov 2003 18:58:46 +0100
Dieter Nützel [EMAIL PROTECTED] wrote:
./PipelineParallelism
./ParallelIso
./ParallelIsoTest
etc.
Do not show _any_ colors.
Only LIBGL_ALWAYS_INDIRECT works.
Some weeks ago, R200_NO_TCL worked.
With recent drivers either use the configuration file or
On Thu, 27 Nov 2003 11:33:23 +
José Fonseca [EMAIL PROTECTED] wrote:
On Tue, Nov 25, 2003 at 10:54:11PM -0500, Marcus Lauer wrote:
Can anyone tell me how I can get the latest mach64 binary snapshot? Up until
the end of October there were available at
Hi all,
the first new snapshots built on freedesktop.org are available at
http://dri.freedesktop.org/~fxkuehl/snapshots. Please test them and let
me know about any problems. Some information about the build:
gcc-2.95.4
glibc-2.3.2
libexpat-1.95.6 statically linked
Using gcc-2.95.4 makes the
On Wed, 26 Nov 2003 07:49:21 +0200
Ville Syrjälä [EMAIL PROTECTED] wrote:
On Tue, Nov 25, 2003 at 10:17:46PM +0100, Felix Kühling wrote:
Hi,
I'm looking into the various templates in Mesa/src/tnl_dd as I'm trying
to port the savage driver to current Mesa. I was wondering what
On Tue, 25 Nov 2003 10:31:21 +
Keith Whitwell [EMAIL PROTECTED] wrote:
Ian Romanick wrote:
Michel Dänzer wrote:
On Mon, 2003-11-24 at 20:01, en ne wrote:
I send you the verbose output and the ldd output.
libexpat.so.1 = not found
This is getting old. This
On Mon, 24 Nov 2003 15:40:12 -0600 (CST)
[EMAIL PROTECTED] wrote:
hi,
I checked out the savage-2-0-0 branch but I can't get the savage drivers
to compile
make World ignores the directory programs/Xserver/hw/drivers/savage
You need to add savage to XF86CardDrivers in config/cf/host.def.
On Tue, 25 Nov 2003 14:48:48 +
José Fonseca [EMAIL PROTECTED] wrote:
[snip]
Sorry. I forgot to flag your reply describing how to link statically and
never remembered the subject again (at that time I was more concerned
with the build failure...) I'm taking care of it now.
Thanks!
Hi,
I'm looking into the various templates in Mesa/src/tnl_dd as I'm trying
to port the savage driver to current Mesa. I was wondering what the
HAVE_HW_FLAT_SHADE macro is doing? It only appears in t_dd_unfilled.h
and it looks like it's doing the exact opposite of what it says:
if
On Thu, 20 Nov 2003 23:06:23 +
Sergey V. Oudaltsov [EMAIL PROTECTED] wrote:
Yess! I found! Strace is the girl's best friend!
r200_dri.so is linked against libexpat.so.1 - while Fedora only provides
libexpat.so.0. That is why libGL.so cannot load r200_dri.so - and
reports missing DR! At
Dear DRI users and testers,
I wrote up more detailed documentation of most configuration options
implemented so far in the Wiki. See
http://dri.sourceforge.net/cgi-bin/moin.cgi/ConfigurationOptions.
Best regards,
Felix
__\|/_____ ___ -
Hi,
The attached patch adds dithering options to the r128 driver. Would
anyone like to test it before I commit?
Best regards,
Felix
__\|/_____ ___ -
Felix ___\_e -_/___/ __\___/ __\_ You can do anything,
Kühling
On Sun, 9 Nov 2003 14:51:32 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
make sure you add the dri and glx modules under the modules section of
your config file. It doesn't look like anything dri related is loading
in the driver. Did you apply the latest code drop from alan or VIA to
401 - 500 of 815 matches
Mail list logo
