2009/12/21 Corbin Simpson <mostawesomed...@gmail.com>: > So, yet another thing that r300 sucks balls at: NPOT textures. We've > been talking it over on IRC, and here's the options. > > 1) Don't do NPOT. Stop advertising PIPE_CAP_NPOT, refuse to accept > non-NPOT dimensions on textures. This sucks because it means that we > don't get GL 2.0, which means most apps (bless their non-compliant > souls) will refuse to attempt GLSL, which means that there's really no > point in continuing this driver. > > 2) Don't do NPOT in the pipe, but do it in the state tracker instead, > as needed. Write up the appropriate fallbacks, and then let ARB_npot > be advertised by the state tracker regardless of whether PIPE_CAP_NPOT > is set. Lots of typing, though. Lots and lots of typing. > > 3) Same as above, but put all the fallbacks in the pipe instead of the > state tracker. I am *really* not fond of this, since PIPE_CAP was not > intended for lies, but it was mentioned in IRC, so I gotta mention it > here. > > 3) The fglrx special: Don't require ARB_npot for advertising GL 2.0. I > figured this wasn't on the table, but you never know... > This is not really about where to implement the fallbacks, but as far as Wine is concerned, we'd mostly care about not triggering those if we can avoid them, e.g. by restrictions on clamping and filtering. We don't care much if GL 2.0 is supported or not, so a hypothetical "MESA_conditional_npot" extension would work for us. Other applications might care though, in which case an extension that allows us to query what situations trigger fallbacks would work for us as well.
The fglrx "solution" mostly just sucks, for an important part because there's (afaik) no real documentation on what the restrictions are, and the reported extensions are now inconsistent with the reported GL version. That said, Wine has code to handle this case now, and I imagine other applications do as well. ------------------------------------------------------------------------------ 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
