Re: [Dri-devel] DRI savage driver status

2003-10-04 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-10-01 Thread Ian Romanick
Felix Kühling wrote: Hello Dimitry, Thanks for the patch. The BCI_LINE_MISC thing is already corrected on the savage-1_0_0-branch. The other things look like attempts to enable DRI on a chip for which DRI is not supported at this point. As was said before, the S3 driver has DRI support for the Sa

Re: [Dri-devel] DRI savage driver status

2003-09-29 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-09-29 Thread Rafael Maximo
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 compat

Re: [Dri-devel] DRI savage driver status

2003-09-29 Thread Dimitry N. Naldaev
В сообщении от 26 Сентябрь 2003 21:47 Felix Kühling написал: > Hello Dimitry, > > Thanks for the patch. The BCI_LINE_MISC thing is already corrected on > the savage-1_0_0-branch. I miss something there: the braces I have added to the mackro Is NOT needed and break some code S3 turn off so I did

Re: [Dri-devel] DRI savage driver status

2003-09-28 Thread Felix Kühling
On Sat, 27 Sep 2003 14:50:02 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote: > At 08:18 AM 27/9/2003, Felix Kühling wrote: [snip] > > DisableTile On worked here but my IRC client looks a little strange, all > texts are unreadable and some checkboxes looks strange too. > > I tried to work with th

Re: [Dri-devel] DRI savage driver status

2003-09-27 Thread Felix Kühling
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 controller: S3 Inc. [ProSavageDDR K

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Alex Deucher
I believe there was some discussion of this on the directfb mailing list. I think the savage chips require a tile based framebuffer for acceleration, but this is incompatible with things that assume a linear based framebuffer. Alex --- Felix K�hling <[EMAIL PROTECTED]> wrote: > I found at leas

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Felix Kühling
Hello Dimitry, Thanks for the patch. The BCI_LINE_MISC thing is already corrected on the savage-1_0_0-branch. The other things look like attempts to enable DRI on a chip for which DRI is not supported at this point. As was said before, the S3 driver has DRI support for the Savage4 series but not t

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Felix Kühling
I think I found it. Try this patch with patch -p0 in xc/programs/Xserver/hw/xfree86/drivers/savage: --- ./savage_driver.c.~1.10.10.5.~ 2003-09-26 14:00:23.0 +0200 +++ ./savage_driver.c 2003-09-26 19:03:30.0 +0200 @@ -2601,7 +2601,7 @@ pScrn = xf86Screens[pScreen->myNum]

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Felix Kühling
I found at least a workaround for the problem. Set Option "DisableTile" "on" in the Device section of XF86Config-4. I think this has something to do with the frame buffer layout. Accellerated stuff seems to get it right. But non-accelerated stuff accesses the frame buffer in the wrong way. Try Op

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Felix Kühling
On Fri, 26 Sep 2003 07:36:02 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote: > At 06:28 AM 26/9/2003, Dimitry N. Naldaev wrote: > >Ð_ Ñ_ообÑ_ении оÑ_ 26 СенÑ_Ñ_бÑ_Ñ_ 2003 14:31 Felix Kühling > >напиÑ_ал: > > > On Fri, 26 Sep 2003 14:03:39 +0600 > > > > > > "Dimitry N. Naldaev" <

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Rafael Maximo
At 06:28 AM 26/9/2003, Dimitry N. Naldaev wrote: В сообщении от 26 Сентябрь 2003 14:31 Felix Kühling написал: > On Fri, 26 Sep 2003 14:03:39 +0600 > > "Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote: > > В сообщении от 26 Сен

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Dimitry N. Naldaev
В сообщении от 26 Сентябрь 2003 14:31 Felix Kühling написал: > On Fri, 26 Sep 2003 14:03:39 +0600 > > "Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote: > > Ð’ сообщении от 26 > > Сентябрь 2003 07:48 Rafael Maximo написал: > > > At 07:38 PM 25/9/2003, Felix Kühling wrote:

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Felix Kühling
On Fri, 26 Sep 2003 14:03:39 +0600 "Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote: > В сообщении от 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 ;-) > >

Re: [Dri-devel] DRI savage driver status

2003-09-26 Thread Dimitry N. Naldaev
В сообщении от 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'm just back from vacation and read about your progress. I'm eager to > >start testing and debugging the new driver.

Re: [Dri-devel] DRI savage driver status

2003-09-25 Thread 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 driver. I think the best thing would be if you could commit your changes to the br

Re: [Dri-devel] DRI savage driver status

2003-09-25 Thread Felix Kühling
On Mon, 22 Sep 2003 11:26:50 +0600 "Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote: > =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1=82= > 20 =D0=A1=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8C 2003 18:05 Rafael Ma= > ximo =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > Hi, >

Re: [Dri-devel] DRI savage driver status

2003-09-25 Thread Felix Kühling
On Sat, 20 Sep 2003 09:05:41 -0300 Rafael Maximo <[EMAIL PROTECTED]> wrote: > > Hi, > > I decided to focus on 2D problem first but i don't know how I can= > =20 > debug the 2D driver and found where is the problem. I would appreciate any= > =20 > information or docs about debugging this

Re: [Dri-devel] DRI savage driver status

2003-09-21 Thread Dimitry N. Naldaev
В сообщении от 20 Сентябрь 2003 18:05 Rafael Maximo написал: > 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 have fixed so

Re: [Dri-devel] DRI savage driver status

2003-09-21 Thread Dimitry N. Naldaev
В сообщении от 21 Сентябрь 2003 05:37 Alex Deucher написал: > you might compare it to Tim's old 2D driver (shipped with 4.3.0) and > see what's changed...assuming his driver works for you in 2D. the guys from S3 have reorganized savage_driver.c so diff between S3 and savage-0-0-1-branch of dri (I

Re: [Dri-devel] DRI savage driver status

2003-09-21 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-09-21 Thread Eric Anholt
On Fri, 2003-09-19 at 20:29, Rafael Maximo wrote: > 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 > > > dri

Re: [Dri-devel] DRI savage driver status

2003-09-20 Thread Alex Deucher
you might compare it to Tim's old 2D driver (shipped with 4.3.0) and see what's changed...assuming his driver works for you in 2D. Alex --- Rafael Maximo <[EMAIL PROTECTED]> wrote: > > Hi, > > I decided to focus on 2D problem first but i don't know how > I can > debug the 2D driver an

Re: [Dri-devel] DRI savage driver status

2003-09-20 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-09-20 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-09-19 Thread Rafael Maximo
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 it is > c

Re: [Dri-devel] DRI savage driver status

2003-09-19 Thread Dimitry N. Naldaev
В сообщении от 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 it is > compiling and i'll test it but i got some other problems. After compiling > ev

Re: [Dri-devel] DRI savage driver status

2003-09-18 Thread Rafael Maximo
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

Re: [Dri-devel] DRI savage driver status

2003-09-17 Thread Rafael Maximo
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 w

Re: [Dri-devel] DRI savage driver status

2003-09-17 Thread Rafael Maximo
I know that the 2D driver is in xc/programs/Xserver/hw/xfree86/drivers/savage but there are a lot of files there and i was expecting something more specific :) i'm trying to avoid a few weeks of studying 2D driver :) I compiled it from savage-1_0_0_-branch and i think it's with

Re: [Dri-devel] DRI savage driver status

2003-09-17 Thread Eric Anholt
On Wed, 2003-09-17 at 19:06, Rafael Maximo wrote: > 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 > everythin

Re: [Dri-devel] DRI savage driver status

2003-09-17 Thread Alex Deucher
for 3D, what 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 --- Ra

[Dri-devel] DRI savage driver status

2003-09-17 Thread 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 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