[Mesa-dev] Mesa (master): nv30: report 8 maximum inputs

[Ilia Mirkin]

On Wed, Feb 12, 2014 at 6:23 PM, Ian Romanick <idr at freedesktop.org> wrote:
> On 02/10/2014 06:16 PM, Ilia Mirkin wrote:
>> On Mon, Feb 10, 2014 at 7:12 PM, Ian Romanick <idr at freedesktop.org> wrote:
>>> On 02/10/2014 02:04 PM, Ilia Mirkin wrote:
>>>> This of course does not preclude them getting clamped/modified in some
>>>> way. Ideally those varying-packing tests would be rewritten in a way
>>>> that better exposes what actually went wrong, but I realize it's not
>>>> easy to add printf("interesting values: %f %f") into a shader.
>>>
>>> Can that hardware render to floating point?  You could try rendering to
>>> a fp FBO, doing glReadPixels, the printf the data.  It's messy, but it
>>> works.
>>
>> The hardware? Yes. But it's disabled in the software. I asked Ben why,
>> and he gave me a reasonable explanation. However that explanation has
>> since escaped my memory, but it's in the irc logs if it's really
>> important.
>
> Probably the patent.  Is it enabled if you build with
> --enable-texture-float?

I'm referring to this in nv30_format.c:

   _(R32G32B32A32_FLOAT  , __V_), //SRV_),

S = sampler view
R = render target
V = vertex buffer

(and a couple of other similarly-commented out float formats)

And the hw docs in envytools seem to suggest it's there.

  -ilia