Thanks...<br>sadly the idea of a generic opencl driver isn't as easy...that would be good if that was available<br><br>kind regards<br>nazim mer<br><br><div class="gmail_quote">On 13 December 2012 15:15, Brecht Van Lommel <span dir="ltr"><<a href="mailto:brechtvanlommel@pandora.be" target="_blank">brechtvanlommel@pandora.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">pocl only supports running OpenCL on the CPU as far as I can tell.<br>
There is no way to have a library automatically support all OpenCL<br>
devices, there is vendor specific code needed for each device.<br>
<span class="HOEnZb"><font color="#888888"><br>
Brecht.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Thu, Dec 13, 2012 at 3:49 PM, Nazim Mer <<a href="mailto:nazim.mer@gmail.com">nazim.mer@gmail.com</a>> wrote:<br>
> Hi,<br>
> sorry for the GPUOcelot thing i forgot that this was mentioned already....<br>
><br>
> as for the Portable opencl driver-wouldn't it be a good idea to incorporate<br>
> this into blender so that opencl becomes supported regardless of the<br>
> vendor..thus introducing a new wave of cycles users,<br>
><br>
> correct me if im wrong- you'd only have to incorporate this(the same way<br>
> blender does with ffmpeg and python) once/every time a new driver comes then<br>
> all opencl capable devices would be usable within cycles..<br>
><br>
> you already have the process where your incorporating Nvidia stuff i.e.<br>
> someone had to test the support for the kepler GPUs(forgot the names of what<br>
> was tested)<br>
><br>
> why cant the same be done for this portable opencl driver...<br>
><br>
><br>
> Kind Regards,<br>
> Nazim Mer<br>
><br>
> On 13 December 2012 14:09, Brecht Van Lommel <<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>><br>
> wrote:<br>
>><br>
>> As I have explained before, I believe that it is a hardware limitation<br>
>> on AMD graphics cards that is giving us trouble. Using different<br>
>> compilers will not help.<br>
>> <a href="http://lists.blender.org/pipermail/bf-cycles/2012-October/000913.html" target="_blank">http://lists.blender.org/pipermail/bf-cycles/2012-October/000913.html</a><br>
>><br>
>> On Thu, Dec 13, 2012 at 1:25 PM, Nazim Mer <<a href="mailto:nazim.mer@gmail.com">nazim.mer@gmail.com</a>> wrote:<br>
>> > could GPUocelot be incorporated into blender so that CUDA works on AMD<br>
>> > gpus<br>
>> > <a href="http://code.google.com/p/gpuocelot/" target="_blank">http://code.google.com/p/gpuocelot/</a><br>
>> ><br>
>> > _______________________________________________<br>
>> > Bf-cycles mailing list<br>
>> > <a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
>> > <a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
>> ><br>
>> _______________________________________________<br>
>> Bf-cycles mailing list<br>
>> <a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Bf-cycles mailing list<br>
> <a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
><br>
_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
</div></div></blockquote></div><br>