Re: [Dri-devel] Mach64 work

2002-03-01 Thread Sergey V. Udaltsov

 I haven't started working on these, so if you choose one of these to work 
 there there wouldn't be chance of we repeating same work.
 I'll keep updating all other mach64_* files until their are in sync with 
 Mesa 4.x and then start on the file of these that you don't choose or help 
 in any other way.
 
 Is this ok with you?
Just hope, after all these wonderful texture-related changes, you wont
forget to update (and notify us testers) binary snapshots:)

Cheers,

Sergey

PS Thank for new slim tarballs. Less then 2 megs - it is cool!

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] Mach64 work

2002-02-28 Thread Leif Delgass

Jose, 

I've been hacking on the tex/texmem/texstate stuff  I just did an update
and it looks like you've done much of the same thing, so I'm sending a
diff for you to compare to your changes  I'm going to download your 
changes and have a look before I continue

I think the next big chunk is the tris/vb stuff, which looks very
different now

-- 
Leif Delgass 
http://wwwretinalburnnet



m64-20022028.diff.gz
Description: mach64 Mesa driver diff


Re: [Dri-devel] Mach64 work

2002-02-28 Thread José Fonseca

On 2002.02.28 10:56 Leif Delgass wrote:
 Jose,
 
 I've been hacking on the tex/texmem/texstate stuff.  I just did an update
 and it looks like you've done much of the same thing, so I'm sending a
 diff for you to compare to your changes.  I'm going to download your
 changes and have a look before I continue.
 

I'm going to look at your diff and I'll integrate your changes. I'm about 
to commit even more changes on other parts soon.

 I think the next big chunk is the tris/vb stuff, which looks very
 different now.
 

I haven't started working on these, so if you choose one of these to work 
there there wouldn't be chance of we repeating same work.
I'll keep updating all other mach64_* files until their are in sync with 
Mesa 4.x and then start on the file of these that you don't choose or help 
in any other way.

Is this ok with you?

 --
 Leif Delgass
 http://www.retinalburn.net
 

Regards,

José Fonseca

_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Mach64 work

2002-02-28 Thread Leif Delgass

On Thu, 28 Feb 2002, José Fonseca wrote:

 On 2002.02.28 10:56 Leif Delgass wrote:
  Jose,
  
  I've been hacking on the tex/texmem/texstate stuff.  I just did an update
  and it looks like you've done much of the same thing, so I'm sending a
  diff for you to compare to your changes.  I'm going to download your
  changes and have a look before I continue.
  
 
 I'm going to look at your diff and I'll integrate your changes. I'm about 
 to commit even more changes on other parts soon.

I took a look at your last commit.  Don't forget the stuff in the new
mach64SetTexImages() in mach64_texstate, it's needed to do some of the
initialization of the driver-specific struct in the texture object which
was removed along with the original mach64CreateTextureObject.  We don't
really need the mip-mapping stuff since the card can't do it.  I was also
toying with the idea of removing some of the redundant parts of that
texture object struct:  the filter functions and clamping could be read
from the gl_texture_object struct when updating the texture unit state.  
The same goes for widthLog2, heightLog2, maxLog2, hasAlpha, and
textelBytes.

Also, it looked to me like the ConvertTexture functions weren't really 
necessary anymore with the new Mesa texture functions.  The r128 driver 
doesn't have them anymore.

  I think the next big chunk is the tris/vb stuff, which looks very
  different now.
  
 
 I haven't started working on these, so if you choose one of these to work 
 there there wouldn't be chance of we repeating same work.
 I'll keep updating all other mach64_* files until their are in sync with 
 Mesa 4.x and then start on the file of these that you don't choose or help 
 in any other way.
 
 Is this ok with you?

ok, I'm going to take a look at mach64_vb.[ch] and mach64_tris.[ch] to see
what need to change (it looks like mach64_tritmp.h will go away).  It's
pretty different from the other drivers at the moment because it's not
using DMA.

  --
  Leif Delgass
  http://www.retinalburn.net
  
 
 Regards,
 
 José Fonseca
 
 _
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com
 

-- 
Leif Delgass 
http://www.retinalburn.net


___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel