> You can already express holes with the current interface by setting > dst_offset of two outputs such that there is a hole between them (e.g. > dst_offset0 = 0, dst_offset1 = 8). I don't think inserting a dummy > output for the hole is needed. > > Also, the commit summary doesn't say that the gallium interface (which > has nothing to do with Draw) is being changed.
Yes, you're right. I made the change the match the semantics of D3D which expects a hole when RegisterIndex is set to max, but now thinking about it we can just as easily handle it on the state tracker side without matching the bahavior. z _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
