[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesa3d-dev
Subject:    Re: [Mesa3d-dev] TGSI simplification branch
From:       michal <michal () vmware ! com>
Date:       2009-11-27 9:16:07
Message-ID: 4B0F98D7.50204 () vmware ! com
[Download RAW message or body]

Keith Whitwell pisze:
> Michal,
> 
> It's really not the job of the shader representation to do this type of versioning \
> between halves of a driver.  If we ever get to a point where we want to do \
> versioning in gallium, we'll want the version control to cover the entire \
> interface, not just the shaders. 
> Given that, and given we won't want to have >1 version of TGSI active within a \
> particular version of gallium, there's no purpose for separate versioning of the \
> shader token stream -- it's just one aspect of the total interface.  If we want to \
> do such a sanity check, it should be done at context or screen creation - well \
> before we ever get around to creating shaders.   
> So I still don't see any point in a shader version token.  The fact that TGSI has \
> been through dramatic changes in its lifetime and still advertises itself as 1.1 \
> illustrates this - it's redundant currently and I don't see any use for it in the \
> future either... 
> 
That's done. It even didn't hurt that much.

Should I go ahead with the patch I sent you earlier?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev


[prev in list] [next in list] [prev in thread] [next in thread]