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 time
At 02:36 PM 18/2/2004, Felix Kühling wrote:
I didn't find any similar string in the driver. It's probably coming
from GLtron.
I committed another fix today. Can you cvs upgrade, enable DMA in
savagedma.h and try if it still locks up in the chromium BSU menu?
Ok, i did that and it still locks up in
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 t
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 multiple
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 locku
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 l
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 leve
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 SF
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 r
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: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 su
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 "Disable
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
matter if i'm run with root 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
Rafa
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 sa
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. Unfort
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
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 - w
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
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.
I'm also wondering why your patch indicate line number 2601 while here it's
on #1757. Are we using the same source? :)
bye.
At 02:11 PM 26/9/2003, Feli
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
¸Ã¸ þà26
áõýÃÂÃÂñÃÂà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'
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 br
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 s
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 .h in the
DRM and the _common.h in
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 hav
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 wo
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
anything
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/
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 http://max.brz.net/glxinfo.1.txt
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
version of mesa are you using? are you using the right
libGL?
For 2D look in xc/programs/Xserver/hw/xfree86/drivers/savage
Try the 2D driver with 3D disabled and see if you still get corruption.
it may be that the 3D side is stomping on the something from the 2D
side.
Alex
--- Rafael Max
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 it is
compiling and i'll test it but i got some other problems. After compiling
everything (2D, 3D, kernel modules, etc.) my screen on xfree 4.3.0 is a
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 usin
aybe
Alan has already fixed it.
bye
At 12:29 PM 16/9/2003, Dimitry N. Naldaev wrote:
÷ ÓÏÏÂÝÅÎÉÉ ÏÔ 13 óÅÎÔÑÂÓØ 2003 00:53 Maximo ÎÁÐÉÓÁÌ:
> As i know CLE266 works only on Xfree86 4.2.0, what i'm doing is make it
> work on xfree86 4.3.0
and what are done and what need to be done ??
As i know CLE266 works only on Xfree86 4.2.0, what i'm doing is make it
work on xfree86 4.3.0
bye.
At 03:01 PM 12/9/2003, Panagiotis D. Ritsos wrote:
Hi..its
silly question time. Isn't the Savage Twister chipset supported when it
comes to 3D and OpenGL? I though it was so...I've seen a webpage ha
I'm working on it. It's a matter of a little more patience :)
bye.
At 06:55 AM 12/9/2003, [EMAIL PROTECTED] wrote:
What About 3D and open-gl support for savage (twister) driver ???
Thank's
and Bye
---
This sf.net email is sponsored by:ThinkGee
Giustiniano,
The savage driver is not working yet. What driver are you using?
bye.
At 07:16 AM 4/9/2003, you wrote:
After building and successfully inserting the savage.o driver, I've tried
to play Warcraft III under linux using winex 3.30: the game starts
(according to the sounds I hea
ot enabled
It's probably here where your problem lies. does your card has enough
memory? People here probably will give you an better explanation than i, so
i'll let them explain.
bye.
Maximo
At 06:28 AM 30/8/2003, Rick Harris wrote:
Hi all,
Just a quick note to put the feelers out on h
| ,'\)|\ `\|
/_.-' _\ \ _:,_ Rafael Maximo " || (
.&#x
Giust,
I intend to work on it, but i'm still reading and studying and any
help will be welcome.
bye
Max
At 04:15 AM 24/7/2003, Giustiniano wrote:
Hi everyone,
I've just subscribed this malinglist, and I'd like to know if there's
someone working on a S3 Savage DRI driver.
If not, I'd lik
Alex,
Good one. I'll try that and post the results here.
Thanks.
Max
At 01:38 PM 10/7/2003, you wrote:
Some tips for those of you messing with the savage driver.
Alex
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.comX-Appa
At 02:16 PM 27/6/2003, Alan Cox wrote:
> When your modifications will be available on Savage-1_0_0-branch?
I've no idea what people want to do about that. My cleaned up stuff wont
work with
2.2 or older 2.4 for example
Could you send me a diff with your changes?
-
At 01:52 PM 27/6/2003, Alan Cox wrote:
On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> Hi,
>
> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> error but when I copied the drm modules do its place at /lib/modules/.
> e tried to load the module into me
Hi,
I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
error but when I copied the drm modules do its place at /lib/modules/.
e tried to load the module into memory i got this unresolved symbol error:
/lib/modules/2.4.21/kernel/drivers/char/drm/savage.o: unresolved sy
At 09:13 AM 24/6/2003, you wrote:
On Tue, Jun 24, 2003 at 06:00:57PM +0600, Dimitry N. Naldaev wrote:
> В сообщении от 24 Июнь 2003 15:19 Alan Hourihane
написал:
> > I'm still looking at the large differences in the 2D driver code, so I
> > thought I'd ask if someone wanted to step up and fix the
At 09:19 PM 17/6/2003, José Fonseca wrote:
> I already read the glossary but what i wanted to know is how the
> interact with each other and what kind of information do they deal with. I
> don't really understand them and I may saying stupid things :).
I understand that you're not familiar
At 05:06 PM 17/6/2003, Andreas Karrenbauer wrote:
Hello,
no it is not finished because it just supports one family of savage chips.
I have a S3 Inc. VT8751 [ProSavageDDR P4M266]. If you look at
the corresponding DDX code you will see that the waiting _for _idle is
really a tricky thing bec
ro na Internet Navegando
http://www.spedia.net/cgi-bin/tz.cgi?run=show_svc&fl=8&vid=1541931
, ,
/ \/ \
(/ //_ \_
.-.\|| . \
\ '-._ _,:__.-"/---\_ \
__/___ '..--'~-&#
At 02:38 PM 15/6/2003, José Fonseca wrote:
> I also noticed in the savage DRM there is a "BCI Initialization"
> that there isn't in the others modules of other devices, what exactaly is
> that?
Please read the archives about it (it's just :
http://marc.theaimsgroup.com/?l=dri-devel&w=2&r
At 06:04 AM 15/6/2003, José Fonseca wrote:
> >The DRM is barely finished. It exists but it doesn't talk with the card
> >at all yet.
>
> This is the kernel modules?
Yes. DRM = kernel module
> The DRM modules to talk with the card, and what
> does "3D Driver" do (xc/lib/GL/mesa/src/drv)?
3D Driver
At 07:14 PM 14/6/2003, José Fonseca wrote:
> Where exactly savage driver
stopped? on DDX driver? What does it still need
> coding?
No. The work in the DDX driver is mostly finished. The DDX was
already
there (on the XFree86 driver) and it was only necessary to make DRI
aware, i.e., to behave nic
At 08:56 PM 13/6/2003, José Fonseca wrote:
On Fri, Jun 13, 2003 at 05:02:36PM -0300, Maximo wrote:
> José,
>
> I think i already read this FAQ twice, at least the sections where
> i think it was important, i'm not afraid of reading documentation neither
> FAQs, but i
one works directly
with the hardware? I would like to know the hierarchy scheme of all these
drivers from the client to the hardware. Can you help me with that?
bye.
Max.
At 03:23 PM 13/6/2003, you wrote:
On Fri, Jun 13, 2003 at 12:38:48PM -0300, Maximo wrote:
> José,
>
> Thank you f
Hi,
I'm really interested but my knowledge about coding a driver is
too limited, i would need some help first before doing any conding.
bye.
Max.
At 12:54 PM 13/6/2003, Andreas Karrenbauer wrote:
José Fonseca wrote:
The second one is if there is anyone working on savage4
drivers
12 AM 13/6/2003, you wrote:
On Fri, Jun 13, 2003 at 12:10:10AM -0300, Maximo wrote:
> I'm new here and i don't know much about developing drivers but i
> really would like to learn, and i'm sorry for the silly questions that i
> may ask.
>
> The first quest
Hi,
I'm new here and i don't know much about developing drivers but i
really would like to learn, and i'm sorry for the silly questions that i
may ask.
The first question is about building the binaries after getting
the source from CVS, it's only "make World" and "make install"
59 matches
Mail list logo
