On Mon, 2009-12-21 at 00:02 -0800, Corbin Simpson wrote:
>
> 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.
These two seem like the most reasonable options. I'm leaning towards 3),
mostly for these reasons:
* It's a limitation of out-of-production hardware, so the onus
should be on the driver[0].
* 2) would require the same workarounds in more state trackers,
e.g. Xorg.
[0] That said, it may make sense to implement it as a utility module.
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
------------------------------------------------------------------------------
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
