On Tue, 02 Jun 2009 16:21:07 +0200
Roland Scheidegger <[email protected]> wrote:
> On 26.05.2009 01:11, Jimmy Rentz wrote:
> > Hello,
> > Why is that gallium overwrites any existing mipmap mag/min
> > filters when aniso is set?
> > Here is the relevant bits from
> > mesa/src/mesa/state_tracker/st_atom_sampler.c (commit
> > 98ae83d5cc73b61826823c915b5c59746c2e85c7)
> > ...
> > if (sampler->max_anisotropy > 1.0) {
> > sampler->min_img_filter = PIPE_TEX_FILTER_ANISO;
> > sampler->mag_img_filter = PIPE_TEX_FILTER_ANISO;
> > }
> >
> > This assumes that all hardware use a different filter
> > for mipmap versus ansio. This is not the case for nvidia
> > since ansio is set separately from the mipmap min/mag
> > filters.
>
> I don't think I understand your question. This code doesn't touch the
> mip filter just min/mag. And i can't see how specifying for instance
> tex_filter_nearest and tex_filter_aniso at the same time would make
> sense, aniso inherently replaces min and mag filters.
>
> Roland
Sorry about the confusion.
I just meant that when you setup a texture on nvidia
cards you always specify the min/mag and ansio filter levels.
Yes, it isn't really bright to set a nearest mag filter
and 4x ansio at the same time. Therefore, I changed my local nouveau
testing code to default the min/mag filters to linear if
you have an ansio filter set.
Jimmy
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
