At 06:25 PM 19/2/2004, Felix Kühling wrote:
Hello S3 Savage users,
---snip---
From the list below I'm going to do (1) and (2) pretty soon. Basically
I'd like to do all of this, all at the same time, if I could. But I have
other things that need attention too. So anybody who has some spare
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 had time to
look into it yet. Can you try if setting SAVAGE_CMD_DMA to 0 in
savagedma.h helps. Just a guess.
Note that
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. Disabling DMA
apparently just masked the problem in some cases. I discussed this with
Alex on IRC yesterday. I'm going to try
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 are
showing correctly and working just fine but i did some tests with Chromium
BSU and it
At 02:06 PM 14/2/2004, Alex Deucher wrote:
--- Rafael Maximo [EMAIL PROTECTED] wrote:
I found some problems here with my savage4, now the textures
are
showing correctly and working just fine but i did some tests with
Chromium
BSU and it lockup on the main menu after sometime
At 07:48 PM 16/1/2004, Alex Deucher wrote:
In all apps I tried so far textures look messed up like you described
before (fonts, lightmaps, normal textures, everything AFAICT). I
tried
quakeforge, q3demo, tuxracer and fgfs. In addition to that I saw the
same corruption of small mipmap levels
At 01:09 PM 16/1/2004, Felix Kühling wrote:
Alex, if you agree, maybe a project admin could open up a new mailing
list, say dri-savage, on sf.net.
If that happen, please tell me, because I'm really interested..
bye.
Rafael Máximo
---
The
At 10:46 AM 9/1/2004, Felix Kühling wrote:
Are you sure that tiled mode is enabled correctly? I think Rafael
reported earlier that 3D (glxgears) worked ok for him with tiled mode
enabled, even though 2D was garbled.
Yes, that's correct but after editing savage_bci.h and defining SAVAGE4 1
bye.
At 07:56 PM 7/1/2004, Alex Deucher wrote:
I tested the driver on my savage4 and I see the 2D corruption maximo
was talking about with tile mode enabled. everything is fine with
tilemode disabled. However, 3D doesn't seem to work in either mode.
With or without tilemode disabled I get random
At 06:28 PM 22/12/2003, Felix Kühling wrote:
- Parts of the screen at top and bottom are black in some modes.
1024x768 is ok. 800x600 too, for me, but another user reported that a
few lines were missing. With 640x480 it's most noticable. Anther user
reported a similar problem at 1280x1024. There
At 02:53 PM 18/12/2003, Felix Kühling wrote:
Take a look at
xc/programs/Xserver/hw/xfree86/drivers/savage/savage_bci.h. There are
conditionals
#if SAVAGE4
...
#endif
Try defining
#define SAVAGE4 1
I did that and things got better now. The 2D is still currupted if i don't
use the option
At 02:58 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
or normal user.
Any help? beside the 3D problem, my screen is corrupted when my
XFree86 starts, the same problem i posted before.
bye.
At 10:54 AM 17/12/2003, Felix Kühling wrote:
Content-Transfer-Encoding: 8bit
On Wed, 17 Dec 2003 10:50:26 -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 in it. The Xserver runs as root,
so that should not be a problem, but I vaguely
Felix,
Very nice. I'll try it latter. What version of Xfree86 did you
test it?
bye.
At 07:19 AM 17/12/2003, Felix Kühling wrote:
Content-Transfer-Encoding: 8bit
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
At 03:31 PM 2/11/2003, Felix Kühling wrote:
On Sun, 2 Nov 2003 00:25:03 +0100
Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I just compiled XFree86 4.2 with the S3 code drop for savage and DRI.
With very little tweaking I got it to work on my notebook, 2D and 3D. Is
the savage_1-0-0-branch based
At 01:24 PM 3/11/2003, Felix Kühling wrote:
Ok. I've committed it on a new savage-2-0-0-branch. Hopefully this
driver works for you. I didn't get display corruption with this one but
there were a few lockups when switching back from another virtual
terminal or when moving a 3D window around.
Same here.
bye.
At 12:16 PM 22/10/2003, Alex Deucher wrote:
Is anyone else getting every meesage that is sent to dri-devel twice or
sometimes even 3 or 4 times? It just started happening over the last
couple days.
Alex
__
Do you Yahoo!?
The New Yahoo! Shopping -
At 01:07 PM 1/10/2003, Ian Romanick wrote:
Just out of curiosity, will the Via driver support the Savage 2000? IIRC,
the rasterization core was based on the Savage4 line, but the TCL unit was
new (obviously). I *know* it wouldn't support the TCL unit, but the
benchmarks that I remember showed
Hi,
I've been working on the savage 2D driver because i was having
problems with it. I checked the current 2D driver on CVS trunk and it
worked just fine here and i decided to take it as a template and modified
the driver on savage-1_0_0-branch and now it's working here and i decided
At 08:18 AM 27/9/2003, Felix Kühling wrote:
On Sat, 27 Sep 2003 00:30:23 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
Felix,
I tried this patch but it looked the same here, it only worked with
DisableTile On. What's your card? i'm using a savage4 chip ID 8A22.
lspci : 01:00.0 VGA compatible
ñÃÂà2003 07:48 Rafael Maximo
ýðÿøÃÂðû:
At 07:38 PM 25/9/2003, Felix Kühling wrote:
Hi Rafael, (a bit confused now, which one is your first name ;-)
I'm just back from vacation and read about your progress. I'm eager to
start testing and debugging the new
At 07:38 PM 25/9/2003, Felix Kühling wrote:
Hi Rafael, (a bit confused now, which one is your first name ;-)
I'm just back from vacation and read about your progress. I'm eager to
start testing and debugging the new driver. I think the best thing would
be if you could commit your changes to the
Dimitry,
You probably mistyped the tag, i think the correct name is
savage-1_0_0-branch
bye.
At 10:45 AM 23/9/2003, Dimitry N. Naldaev wrote:
I got an error :-(
[EMAIL PROTECTED]:~/wrk/dri/xc/xc/util/misc$ cvs -z3
-d:pserver:[EMAIL PROTECTED]:/cvs/dri update -rsavage_1-0-0_branch
cvs
The drmCommandRead and friends are a wrapper for ioctl. I think the
idea was that they were for portability, but I can't remember. Note
that the numbering of the commands for drmCommand* are different from
the ioctl numbers (subtract 0x40 iirc) -- look at the card.h in the
DRM and the
Hi,
I decided to focus on 2D problem first but i don't know how I can
debug the 2D driver and found where is the problem. I would appreciate any
information or docs about debugging this kind of problem.
I'm using the 2D driver on savage_1-0-0_branch and i didn't change
I already sent this message, but i think something happened
because i didn't receivea copy from the list, that's why i'm sending again.
-begin-
Hi,
I decided to focus on 2D problem first but i don't know how I can
debug the 2D driver and found where is the problem. I
Brian,
I'm interested seeing the savage driver working on XFfree86 4.3.0 with mesa
5.0.x, you are using a savage driver that is supposed to work on xfree86
4.2.0 and i'm working on the same driver but trying to make it works on
xfree86 4.3.0
bye.
At 08:28 PM 20/9/2003, Brian Penix wrote:
I
At 12:44 AM 19/9/2003, Dimitry N. Naldaev wrote:
Ð ÑообÑении Ð¾Ñ 18 СенÑÑбÑÑ 2003 08:06 Rafael Maximo
напиÑал:
Hi,
Some of you already know that i'm trying to work on the savage
driver, i'm working on the 3D driver (/lib/GL/mesa/src/drv) and now
You were right!, there was some missing symbols and now it's fixed but now
a got another problem, glxinfo shows this message:
Can't alloc DMA memory(system and agp)
name of display: :0.0
display: :0 screen: 0
direct rendering: No
The complete glxinfo output is in
I'm getting a similar problem on my xfree86 4.3.0, the 2D screen is
corrupted but it looks better than yours :) but here glxinfo reports Direct
Rendering disable. Your XFree86 log shows something not good:
(--) SAVAGEInitMC: There is no enough memory!
Someone also reported a similar problem
I forgot to mention, i also want an opinion about this line on XFree86
log:
(II) SAVAGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0,
hwp-PIOOffset is 0x
This line is repeated several times and I would like to know what
does it mean. Is this normal?
bye.
At 11:06 PM 17/9/2003, Rafael Maximo
Ok, i make lib/GL/mesa/src/drv/savage compile but it doesn't mean that its
working but i noticed yesterday that the 2D driver was not compiling
(/programs/Xserver/hw/xfree86/drivers/savage - i thinks this is the
directory, not sure) but i didn't have time to look at the code yet, maybe
Alan
33 matches
Mail list logo
