No idea. It could be tested either with Direct3D 9 on Windows (assuming the driver does not reject that), by modifying the Mesa source or by using Gallium directly.
The issue is whether to have the Gallium API support it by splitting max_anisotropy into max_mag_anisotropy or max_min_anisotropy or not do that, and have a single max_anisotropy value (which, after removing PIPE_TEX_FILTER_ANISO, would control whether anisotropic filter is enabled or not in addition to the number of samples). Currently it can be done because there is a PIPE_TEX_FILTER_ANISO, but that doesn't work well for nVidia hardware, which (according to nVidia claims and reverse engineered registers) supports anisotropic nearest (in addition to bilinear) filtering.
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
