On Sat, 21 Feb 2004 16:41:56 +
José Fonseca <[EMAIL PROTECTED]> wrote:
> The errors were caused by an attemp to list files in
> /home/groups/d/dr/dri/htdocs/snapshots which no longer exists after the
> snapshots been move to d.f.o. I fixed
> it just so that it shows the full page without error
On Sat, 21 Feb 2004 02:36:26 +
Sérgio Monteiro Basto <[EMAIL PROTECTED]> wrote:
> On Thu, 2004-02-19 at 15:46, Felix Kühling wrote:
> > I don't see a reason to mess with Mesa on the savage-2-0-0-branch now.
>
> ok,
> This is not my code, this is Brian Pau
On Fri, 20 Feb 2004 17:29:07 -0800
Tim Roberts <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
>
> >Felix can probably phrase this better than I since he has worked more
> >closely with the 3D code. however, I think what he is asking is how
> >should vertex commends be formatted when sent to th
Hi,
DPMS never worked on my notebook with ProSavageDDR. The problem is that
the register that controls HSync and VSync signals of the CRT doesn't
have any effect on the LCD display. The attached patch disables the LCD
display via the bios if the DPMS mode is anything but "ON". Alex, if you
think t
On Fri, 20 Feb 2004 09:25:50 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > On Tue, 17 Feb 2004 12:38:04 -0800
> > Alex Deucher <[EMAIL PROTECTED]> wrote:
> >
> > > CVSROOT: /cvs/dri
> > > Module name: xc
> > > Repository: xc/
On Fri, 20 Feb 2004 08:28:55 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > On Tue, 17 Feb 2004 12:38:04 -0800
> > Alex Deucher <[EMAIL PROTECTED]> wrote:
> >
> > > CVSROOT: /cvs/dri
> > > Module name: xc
> > > Repository: xc/
On Fri, 20 Feb 2004 14:55:55 +
Alan Hourihane <[EMAIL PROTECTED]> wrote:
> Felix,
>
> How about dropping your current DRI savage driver into the Mesa trunk (6.1)
> and whipping the driver into shape with the current DRI trunk.
Are you suggesting to continue development on DRI trunk or make a
On Fri, 20 Feb 2004 08:04:43 -0800
Ian Romanick <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
>
> > The last one is the easier one I think. In savagetex.c in
> > savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty
> > fancy computation of th
On Thu, 19 Feb 2004 18:58:25 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
[snip]
>
> I really interested on helping, specially on savage4 driver because is the
> only one i have access, unfortunately i don't have much experience on
> hardware programing but i'm learning a lot checking the sav
On Thu, 19 Feb 2004 18:26:50 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > Hello S3 Savage users,
> >
> [snip]
>
> Felix,
>
>I'd like to give you a hand on the 3D driver while I still have some
> free time, but I have to admit, I'm
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher <[EMAIL PROTECTED]> wrote:
> CVSROOT: /cvs/dri
> Module name: xc
> Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
> Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
>
> Log message:
> - fix console corruption. rather
Hello S3 Savage users,
The most basic grunt work on the Savage 3D driver has been done in the
last three months. The driver was ported to Mesa 5 and support for the
Savage3D chip family was added. The result is available in CVS on the
savage-2-0-0-branch in DRI CVS. Now I consider the driver prett
[snip]
> diff -urN /tmp/wiki.qjQHTM/wiki/text/Troubleshooting
> /home/groups/d/dr/dri/wiki/text/Troubleshooting
> --- /tmp/wiki.qjQHTM/wiki/text/Troubleshooting2003-10-01 11:14:08.0
> -0700
> +++ /home/groups/d/dr/dri/wiki/text/Troubleshooting 2004-02-18 18:54:27.0
> -0
Hi Sérgio,
first off, I appreciate your interest in the savage driver and your
initiative. I'll comment on your proposals below. I'm going to send sort
of a savage roadmap to the list soon which will outline my plans for the
3D driver for the next couple of months. I'm sure there will be items on
On Thu, 19 Feb 2004 11:24:27 +
Alan Cox <[EMAIL PROTECTED]> wrote:
> On Iau, 2004-02-19 at 02:02, Alex Deucher wrote:
> > 2D: do to a bug in S3's code, 2D accel was never enabled when the DRI
> > was active. I've managed to get 2D accel working again. one question
> > I have, I assume xf86In
On Tue, 17 Feb 2004 09:41:55 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 09:16 AM 17/2/2004, Felix Kühling wrote:
>
> >That's what I hoped. But unfortunately that's not the case. Now the
> >driver locks up in other situations that were fine before. Disab
> > If I boot with VesaFB and switch VTs it restores a graphics mode now.
> > But it's messed up. At the top of the screen there is a blue stripe,
> > maybe 32 pixels heigh, then there is some heavily distorted and
> > unreadable black and white console text up to about the middle of the
> > screen
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher <[EMAIL PROTECTED]> wrote:
> CVSROOT: /cvs/dri
> Module name: xc
> Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
> Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
>
> Log message:
> - fix console corruption. rather
On Tue, 17 Feb 2004 17:46:48 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
[snip]
> The GLX visual matching code is pretty much driver-independant, so it's
> odd this would only be a problem with the mga driver. That said, there
> were some changes in that area since XFree86 4.3, but I don't
Hi,
I just took a brief look at the savage 2D driver. It looks like the COB
is never enabled. On Savage4 and ProSavages it explicitly left disabled
in SavageInitialize2DEngine. On the Savage3D/MX/IX that function is
never even called. Yet I'm surprised that the 3D driver doesn't crash
and burn all
On Tue, 17 Feb 2004 08:59:20 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 07:45 PM 14/2/2004, Felix Kühling wrote:
>
> >I'm downloading the game just now. :) I get another reproducable hard
> >lockup when the glblur xscreensaver hack exits. I havn't ha
Hi,
The Savage driver now works on SavageIX (and probably Savage3D and
SavageMX) with 3D acceleration. I just committed the last few pieces to
the savage-2-0-0-branch. There are a few known issues left to sort out:
- flat shading
(Savage IX uses the first vertex's color instead of the last one
Which hardware/driver are you using under Linux?
I just became aware of a hardware limitation in several drivers (mga,
r128, savage). They can do multi texturing, but if multi texturing and
projective textures are used at the same time they fall back to software
rendering. For example quake2 gets
Hi Cristiano,
short answer to a long mail: The Savage driver does not support
Savage2000 chips at the moment. We have no hardware documentation nor a
reference driver implementation. Unless this changes it's unlikely that
Savage2000 support will be available any time soon. :-/
At the moment the d
On Sat, 14 Feb 2004 12:45:45 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> First i would like to say that Alex and Felix are doing a great
> job with savage driver and every day it's getting better.
>
> I found some problems here with my savage4, now the textures ar
On Sat, 14 Feb 2004 13:27:03 -0800
James Jones <[EMAIL PROTECTED]> wrote:
> Yeah, got a couple things here.
>
> First, the dmesg. the dma test is failing. It worked fine on the old branch.
> This of course happens when starting X. Here's a dmesg clip:
[snip]
>
> As for the glxgears thing, I
On Tue, 10 Feb 2004 22:38:58 +
Sérgio Monteiro Basto <[EMAIL PROTECTED]> wrote:
[snip]
> Well looking at rubik cube screen saver, we have (I think) one bug that
> I think I know this bug from mesa code in same source, so update the
> Mesa code may could be a good idea, that I am able to do it,
On Fri, 13 Feb 2004 00:13:37 +0100
Dieter Nützel <[EMAIL PROTECTED]> wrote:
> Hello Ian,
>
> I have some time now and started with a rollback to cvs -D 07/02/2003.
> Some "rate" vs "period" fixes need but then I hang at some XFree basic stuff
> (xkb).
>
> -c -o xkb/xf86KillSrv.o xkb/xf86Kil
On Thu, 12 Feb 2004 14:01:01 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Thu, 12 Feb 2004 10:17:11 + (GMT)
> Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> > >
> > > While I'm at it (see driinterface-0-0-3-branch mails) I could update the
On Thu, 12 Feb 2004 10:38:24 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Wed, 11 Feb 2004 18:56:39 -0800
> Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> [snip]
> > In-progress. Please test this branch! :) Would it be possible to make
> > the R200 n
On Thu, 12 Feb 2004 10:17:11 + (GMT)
Dave Airlie <[EMAIL PROTECTED]> wrote:
> >
> > While I'm at it (see driinterface-0-0-3-branch mails) I could update the
> > snapshot scripts to build mach64-0-0-7-branch snapshots.
>
> please do it, I'm sure a bit more testing would help a lot ...
Done. I
On Thu, 12 Feb 2004 10:38:24 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Wed, 11 Feb 2004 18:56:39 -0800
> Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> [snip]
> > In-progress. Please test this branch! :) Would it be possible to make
> > the R200 n
On Thu, 12 Feb 2004 06:42:29 + (GMT)
Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> Okay the last few fixes make tuxracer and glxgears work again, so the new
> branch should be as useable as the old one, I think there are still a few
> cleanups in the native vertex code (using macros for a few th
On Wed, 11 Feb 2004 18:56:39 -0800
Ian Romanick <[EMAIL PROTECTED]> wrote:
[snip]
> In-progress. Please test this branch! :) Would it be possible to make
> the R200 nightly snapshot come from the branch instead (or in addition
> to) the trunk? I'd like to merge to the trunk next Thursday
> (
On Tue, 10 Feb 2004 23:51:58 +
Sérgio Monteiro Basto <[EMAIL PROTECTED]> wrote:
> On Tue, 2004-02-10 at 22:38, Sérgio Monteiro Basto wrote:
> > On Tue, 2004-02-10 at 13:27, Felix Kühling wrote:
> >
> > > > I realize that xc/extras/Mesa is almost the same
On Tue, 10 Feb 2004 06:46:16 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
[snip]
>
> hmmm... that's probably because I used the SetTextMode() bios call on
> close screen and VT switches. I'll have dig into that more and see if
> I can get
On Mon, 9 Feb 2004 16:40:19 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
> I think I fixed the problem that caused your prosavage to fail. I
> forgot to add PROSAVAGEDDR and TWISTER to the bci setup function
> (SavageInitialize2d()) in savage_accel.c. That should fix it, but I
> don't hav
On Mon, 09 Feb 2004 09:14:28 -0800
Ian Romanick <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
>
> > I tracked down the Savage4 texture corruption problem last night. A
> > patch is attached, but it'll break ProSavages. A real solution will have
> > to wa
Hi,
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is terribly inefficient the way it implements
tiling and su
On Mon, 9 Feb 2004 06:10:26 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
[snip]
> I'm going to commit my current integration work now. This will break
> Xv, tile mode, and console mode for the time being, but I hope to
> rectify that soon.
On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > Alex,
> >
> > I'm working on 3D support for Savage IX right now. I've added
> > register
> > structures for SavageIX. Now I need to find out the chipset type in
>
Alex,
I'm working on 3D support for Savage IX right now. I've added register
structures for SavageIX. Now I need to find out the chipset type in the
3D driver. That requires a few small modifications to the 2D driver. I'm
not sure if I should work with the old or your new 2D driver. I'd prefer
to
On Fri, 6 Feb 2004 09:36:48 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
[snip]
> http://www.botchco.com/alex/savage/savage-20040206.tar.gz
Nice work! I tested 2D and 3D on the savage4. It works as well as the S3
driver and fixes the mode setting problem I reported earlier (stretching
1279
Hi,
after updating and recompiling DRI direct rendering was not working. I
even tried make World to be sure. LIBGL_DEBUG=verbose glxgears shows
this problem:
libGL: XF86DRIGetClientDriverName: 4.0.1 radeon (screen 0)
libGL: OpenDriver: trying /usr/X11R6-DRI/lib/modules/dri/radeon_dri.so
libGL err
On Thu, 29 Jan 2004 10:52:25 -0800
Eric Anholt <[EMAIL PROTECTED]> wrote:
> On Thu, 2004-01-29 at 07:15, Felix Kühling wrote:
> > Thanks. I see you used my versions of the scripts as a basis. BTW, these
> > scripts are also in CVS, though your latest changes are obviously
Thanks. I see you used my versions of the scripts as a basis. BTW, these
scripts are also in CVS, though your latest changes are obviously not
committed yet. Are you going to keep maintaining the scripts in CVS?
Regards,
Felix
On Wed, 28 Jan 2004 14:35:19 -0800
Eric Anholt <[EMAIL PROTECTED]> w
One more thing I noticed: extras/xdriinfo.bz2 is no longer needed. It's
included in the snapshots. So in order to avoid unnecessary confusion it
could be removed from the download area.
Regards,
Felix
---
The SF.Net email is sponsored by Ecli
Hi,
after a CVS upgrade last night I got two some assertions in the radeon
driver. One happened when exiting from glxgears in radeonDeleteTexture.
Commenting out the assert statement helped.
I got the other one in Torcs when entering the game. Here's a complete
backtrace.
torcs: radeon_state.c:7
I got the same after a cvs upgrade of the trunk last night with
LIBGL_DRIVERS_PATH still set to my savage-2-0-0-branch installation.
On Fri, 23 Jan 2004 02:28:12 +0100
Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> I'm normally using the libGL from my 2003.10.05 snapshot packages, and
> the curren
On Wed, 28 Jan 2004 09:30:47 -0800
Tim Roberts <[EMAIL PROTECTED]> wrote:
> For those of you who experience the weird refresh rate settings using
> the 1.1.27t driver on your ProSavage-DDR, there now seem to be TWO
> workarounds. The first, which I have been recommending, is to disable
> the u
On Mon, 26 Jan 2004 23:10:33 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
[snip]
> >
> > torcs: radeon_state.c:741: radeonUpdateSpecular: Assertion `(p & (1 << 21)) == 0'
> > failed.
> >
[snip]
> You get that
On Mon, 26 Jan 2004 16:03:02 -0800 (PST)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> On Mon, 26 Jan 2004, Felix Kühling wrote:
> >
> > after a CVS upgrade last night I got two some assertions in the radeon
> > driver. One happened when exiting from g
(resending due to SF mailing list problems ...)
Hi,
after a CVS upgrade last night I got two some assertions in the radeon
driver. One happened when exiting from glxgears in radeonDeleteTexture.
Commenting out the assert statement helped.
I got the other one in Torcs when entering the game. Here
On Thu, 22 Jan 2004 00:16:52 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
[snip]
> xdemos/glthreads: I didn't have the courage to test this (I just didn't
> feel like rebooting ;-)) - in the past it always locked up immediately
> when at least 33 threads were specified, or locked up after
On Thu, 22 Jan 2004 00:17:54 +0100
Michel Dänzer <[EMAIL PROTECTED]> wrote:
[snip]
> > btw the same code is also in the radeon driver. If endgame doesn't work
> > there correctly, it's likely for the same reason I guess.
>
> Yeah, and I wonder whether attenuation works there or needs some of the
On Wed, 21 Jan 2004 02:02:58 +0100
Andreas Happe <[EMAIL PROTECTED]> wrote:
> On 2004-01-17, Micha Feigin <[EMAIL PROTECTED]> wrote:
> > If I got things right then the dri tree is not a complete X tree. You
> > need a working X installation to install over. It installs only the
> > modified files.
On Mon, 19 Jan 2004 09:53:41 -0700
Brian Paul <[EMAIL PROTECTED]> wrote:
> This looks like a problem with the XML configuration feature.
> Anyone?
>
> -Brian
>
The error message
Unable to open radeon_dri.so: /home/rob/src/Mesa/lib/radeon_dri.so:
undefined symbol: XML_SetElementHandler
would
On Sun, 18 Jan 2004 16:16:13 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
[snip]
> I found it. :) Comparison with the Utah driver helped once more. I'm
> attaching two new patches, one for the 2D driver, one for the 3D driver.
> They are against the latest savage-2-0
On Sat, 17 Jan 2004 17:52:07 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > 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
> > b
On Sun, 18 Jan 2004 01:30:24 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
[snip]
> P.S.: drawing everything as software fallbacks doesn't always work on my
> ProSavage. With glxgears and some xscreensaver hacks I tried the window
> stays black. In flightgear some polys are
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 acces
Quick update...
On Sat, 17 Jan 2004 17:23:40 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> hard when I start glxgears. :( It's pretty hard to find out what causes
> the lockup at this point. Tim Roberts mentioned a bug in Savage4 and
> ProSavages that causes lockups w
Ok,
I plugged this Savage IX into my box now. The best way to work with it
for now seems to be to explicitly set a virtual desktop size. It will
only show 640x480. The CrtOnly option is not really helpful ATM.
I did some first tests with 3D. First it used to hang in WAIT_FOR_FIFO
and later in get
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 s
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
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 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
ds,
Felix
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
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:
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 regis
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 dro
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 18
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
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 behaviou
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 confuse
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]> wrot
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 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
> > trackball
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.
> tex
On Mon, 12 Jan 2004 18:31:01 -0200
Felipe Almeida Lessa <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I confess I'm really confused about Linux vs. Savage4 suport. My ol' computer has a
> Diamond Stealth III since early 2001, and in that epoch I didn't use Linux, and so
> was happy with 3D grap
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. Met
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
> > c
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 b
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 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
The span stuff itself is in savagespan.c in the Mesa driver. However, i
I just noticed that your changes broke the line pitch in the span
functions (again). You see the effect when you run xscreensaver hacks with
-fps. I'll see if I can fix it once more. ;-)
Felix
On Fri, 9 Jan 2004 12:45:10 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
> The attached patch is
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 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
> SavageEnableMo
heidegger wrote:
> > Based 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 indee
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
> acce
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 funct
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 co
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
On Wed, 7 Jan 2004 16:41:38 +0100 (CET)
Pavel harry_x Palát <[EMAIL PROTECTED]> wrote:
> > Looks like a problem with the new def_max_anisotropy option. It's the
> > first floating-point option. I don't understand why this is happening,
> > though. It works just fine in the radeon driver and the de
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 Sun, 4 Jan 2004 19:30:45 +0100
Dieter Nützel <[EMAIL PROTECTED]> wrote:
> Am Samstag, 03. Januar 2004 04:52 schrieb Felix Kühling:
> > Hi,
> >
> > this is referring to the a very reproducable lockup that occurred with
> > glaxium on r100 hardware. Severa
: 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 shor
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
> >
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
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/ConfigurationForDeveloper
301 - 400 of 843 matches
Mail list logo
