I pushed it. Thanks Nicholas.
Stéphane
On Thu, Sep 22, 2016 at 9:40 AM, Roland Scheidegger
wrote:
> Am 22.09.2016 um 17:40 schrieb Emil Velikov:
> > Hi Nicholas,
> >
> > On 26 August 2016 at 00:31, Nicholas Bishop
> wrote:
> >> From: Nicholas Bishop
> >>
> >> On Intel Pineview M hardware, th
Am 22.09.2016 um 17:40 schrieb Emil Velikov:
> Hi Nicholas,
>
> On 26 August 2016 at 00:31, Nicholas Bishop wrote:
>> From: Nicholas Bishop
>>
>> On Intel Pineview M hardware, the i915 gallium driver doesn't output
>> the correct gl_FragCoord. It seems to always have an X coord of 0.0
>> and a Y
On Thu, Sep 22, 2016 at 8:40 AM, Emil Velikov
wrote:
> Hi Nicholas,
>
> On 26 August 2016 at 00:31, Nicholas Bishop wrote:
> > From: Nicholas Bishop
> >
> > On Intel Pineview M hardware, the i915 gallium driver doesn't output
> > the correct gl_FragCoord. It seems to always have an X coord of 0
Hi Nicholas,
On 26 August 2016 at 00:31, Nicholas Bishop wrote:
> From: Nicholas Bishop
>
> On Intel Pineview M hardware, the i915 gallium driver doesn't output
> the correct gl_FragCoord. It seems to always have an X coord of 0.0
> and a Y coord of the window's height in pixels, e.g. 600.0f or
From: Nicholas Bishop
On Intel Pineview M hardware, the i915 gallium driver doesn't output
the correct gl_FragCoord. It seems to always have an X coord of 0.0
and a Y coord of the window's height in pixels, e.g. 600.0f or such.
I believe this is a regression caused in part by this commit:
afa035
