I am curious, how does this bit change the shader (or shader operations, export, or whatever). I guess you're referring to the bit saying "Drives dx10 clamp in spi_sq newWave cmd" settable separately for each shader type but that doesn't mean much to me :-).
Roland Am 10.12.2014 um 21:16 schrieb Marek Olšák: > Wow, yes! The DX10_CLAMP bit fixes this issue too. I guess we don't > have to use legacy instructions now. > > Marek > > On Mon, Dec 8, 2014 at 5:05 AM, Michel Dänzer <mic...@daenzer.net> wrote: >> On 04.12.2014 21:34, Marek Olšák wrote: >>> From: Marek Olšák <marek.ol...@amd.com> >>> >>> Discussion: >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.freedesktop.org_show-5Fbug.cgi-3Fid-3D83510-23c8&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_I&m=wYbokNJOnFBGstvWMmYoGPCVEP9QfPQw0wnRl42Jw0Q&s=rVzVSrX2MYZiMDzqraJyiS53MdcsrSnVfVdG6WQyWOs&e= >>> >> >> I wonder if we could avoid at least some of this trouble using the DX10 >> / IEEE bits in the shader MODE register. >> >> >> -- >> Earthling Michel Dänzer | >> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amd.com_&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_I&m=wYbokNJOnFBGstvWMmYoGPCVEP9QfPQw0wnRl42Jw0Q&s=j8yXvz073rSQDrLT-gDX9jMI3wFgZNH4XNK78KVjwF4&e= >> >> Libre software enthusiast | Mesa and X developer > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Ddev&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_I&m=wYbokNJOnFBGstvWMmYoGPCVEP9QfPQw0wnRl42Jw0Q&s=6RdqH9tgdRJ6eAyvHuK6hKxQ2yBJY8p0v3vGiVT1Y20&e= > > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
