> Because there is some expectation (with the exception of the private
> flags) this is state set by the state tracker.
Yes, currently it's this way, but I think that overall, this is suboptimal.
For instance, I think that drivers should override the bind flags,
setting them to what the resource a
On 17.08.2010 17:48, Luca Barbieri wrote:
>> Well I don't like drivers changing the hints flag on their own,
>> overwriting what the state tracker set. Hence the suggestion to just
>> always use normalized coords unless the driver can't handle it (which
>> can be a usual global query).
>
> In my s
> Well I don't like drivers changing the hints flag on their own,
> overwriting what the state tracker set. Hence the suggestion to just
> always use normalized coords unless the driver can't handle it (which
> can be a usual global query).
In my second patchset, those flags are owned by the drive
On 17.08.2010 16:12, Luca Barbieri wrote:
>> I don't like it, imho adds too much interface clutter with little gain
>> (for most hardware).
> There is a tradeoff here between a clean and general but intrusive
> approach (this one), and a minimal but conceptually imperfect approach
> (the previous o
> I don't like it, imho adds too much interface clutter with little gain
> (for most hardware).
There is a tradeoff here between a clean and general but intrusive
approach (this one), and a minimal but conceptually imperfect approach
(the previous one).
Keith didn't seem to like the previous minima
On 17.08.2010 09:09, Luca Barbieri wrote:
> This is a new approach to the coordinate normalization issue.
> I only compile tested this, and posted it to find out if I'm on the right
> track, and will do more testing if so.
>
> On the state tracker -> driver front, I no longer have any resource fla
This is a new approach to the coordinate normalization issue.
I only compile tested this, and posted it to find out if I'm on the right
track, and will do more testing if so.
On the state tracker -> driver front, I no longer have any resource flags and
instead split PIPE_BIND_SAMPLER_VIEW into 4 s
