From: M. B. <ser...@ne...> - 2004-02-19 14:59:10
Attachments:
ff.diff
|
I compared sources of Mesa-5.0.2 final release http://prdownloads.sourceforge.net/mesa3d/MesaLib-5.0.2.tar.gz?download http://prdownloads.sourceforge.net/mesa3d/MesaDemos-5.0.2.tar.gz?download with mesa on this tree, the sources are not exactly equal, so I send to you my proposal patch to put sources in last version of Mesa-5.0.2. Can be applied like this: cd xc/xc; cat ff.diff | patch -p0. I test it today and I don't see any regression, but without any improvement as well.=20 I am thinking, as well, do a patch kernel for integrate dri module in kernel with this tree code and with ac code from kernel 2.4.22-ac4. For compile kernel with savage module, instated have compile it after compile kernel. If anyone have some of this stuff already made it please help me to save my time on doing it again. Sorry for my terrible English if something is not clear please ask me again. Thanks=20 --=20 S=E9rgio M. B. |
From: Felix <fx...@gm...> - 2004-02-19 15:52:38
|
Hi S=E9rgio, 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 the list for you to pick up. ;-) On Thu, 19 Feb 2004 14:52:48 +0000 S=E9rgio Monteiro Basto <ser...@ne...> wrote: > I compared sources of Mesa-5.0.2 final release > http://prdownloads.sourceforge.net/mesa3d/MesaLib-5.0.2.tar.gz?download > http://prdownloads.sourceforge.net/mesa3d/MesaDemos-5.0.2.tar.gz?download > with mesa on this tree, the sources are not exactly equal, so I send to > you my proposal patch to put sources in last version of Mesa-5.0.2. > Can be applied like this: cd xc/xc; cat ff.diff | patch -p0. >=20 > I test it today and I don't see any regression, but without any > improvement as well.=20 The Savage 3D driver will eventually move to Mesa CVS like the drivers on the trunk did. Then they will use the most up-to-date Mesa development code. If you don't see any improvements from your patch then I don't see a reason to mess with Mesa on the savage-2-0-0-branch now. >=20 > I am thinking, as well, do a patch kernel for integrate dri module in > kernel with this tree code and with ac code from kernel 2.4.22-ac4. > For compile kernel with savage module, instated have compile it after > compile kernel. It is probably a good idea to keep integration into the linux kernel in mind. Eventually we want the Savage DRM driver in the kernel source. Until then the kernel module will change a lot though. During that time it will be important to use the most current kernel module with the latest 3D driver. Therefore splitting the source trees is not a good idea right now (IMHO anyway). >=20 > If anyone have some of this stuff already made it please help me to save > my time on doing it again. >=20 > Sorry for my terrible English if something is not clear please ask me > again. >=20 > Thanks=20 >=20 > --=20 > S=E9rgio M. B. >=20 Best regards, Felix |
From: M. B. <ser...@ne...> - 2004-02-21 02:59:31
|
On Thu, 2004-02-19 at 15:46, Felix K=FChling 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 Paul code.=20 So please apply, I remember, at the time of release Mesa-5.0.2, Brian release one version of Mesa-5.0.2 to test, after this, he did some corrections, I think we are using the beta version. I think this code is safe because is one copy of last version of Mesa-5.0.2. You can check by your self!.=20 At least apply this one : - xoffset, yoffset, xoffset, /* dest offsets */ + xoffset, yoffset, zoffset, /* dest offsets */ > It is probably a good idea to keep integration into the linux kernel in > mind. Eventually we want the Savage DRM driver in the kernel source. > Until then the kernel module will change a lot though. During that time > it will be important to use the most current kernel module with the > latest 3D driver. Therefore splitting the source trees is not a good > idea right now (IMHO anyway). I am not thinking in splitting the code, you will see :) > Best regards, Best regards and many thanks=20 --=20 S=E9rgio M. B. |
From: Felix <fx...@gm...> - 2004-02-21 15:38:49
|
On Sat, 21 Feb 2004 02:36:26 +0000 S=E9rgio Monteiro Basto <ser...@ne...> wrote: > On Thu, 2004-02-19 at 15:46, Felix K=FChling wrote: > > I don't see a reason to mess with Mesa on the savage-2-0-0-branch now. >=20 > ok, > This is not my code, this is Brian Paul code.=20 > So please apply, I remember, at the time of release Mesa-5.0.2, Brian > release one version of Mesa-5.0.2 to test, after this, he did some > corrections, I think we are using the beta version. I think this code is > safe because is one copy of last version of Mesa-5.0.2. You can check by > your self!.=20 > At least apply this one : > - xoffset, yoffset, xoffset, /* dest offsets */ > + xoffset, yoffset, zoffset, /* dest offsets */ After some engouraging words from Alan Hourihane I'm going to move the 3D driver to Mesa CVS this weekend. That should solve all problems you have with Mesa (and introduce new ones ;-). At the same time=20 >=20 >=20 > > It is probably a good idea to keep integration into the linux kernel in > > mind. Eventually we want the Savage DRM driver in the kernel source. > > Until then the kernel module will change a lot though. During that time > > it will be important to use the most current kernel module with the > > latest 3D driver. Therefore splitting the source trees is not a good > > idea right now (IMHO anyway). > I am not thinking in splitting the code, you will see :) Ok. Felix |