Brecht Van Lommel
brechtvanlommel at pandora.be
Thu Dec 13 16:15:20 CET 2012
pocl only supports running OpenCL on the CPU as far as I can tell.
There is no way to have a library automatically support all OpenCL
devices, there is vendor specific code needed for each device.
On Thu, Dec 13, 2012 at 3:49 PM, Nazim Mer <nazim.mer at gmail.com> wrote:
> sorry for the GPUOcelot thing i forgot that this was mentioned already....
> as for the Portable opencl driver-wouldn't it be a good idea to incorporate
> this into blender so that opencl becomes supported regardless of the
> vendor..thus introducing a new wave of cycles users,
> correct me if im wrong- you'd only have to incorporate this(the same way
> blender does with ffmpeg and python) once/every time a new driver comes then
> all opencl capable devices would be usable within cycles..
> you already have the process where your incorporating Nvidia stuff i.e.
> someone had to test the support for the kepler GPUs(forgot the names of what
> was tested)
> why cant the same be done for this portable opencl driver...
> Kind Regards,
> Nazim Mer
> On 13 December 2012 14:09, Brecht Van Lommel <brechtvanlommel at pandora.be>
>> As I have explained before, I believe that it is a hardware limitation
>> on AMD graphics cards that is giving us trouble. Using different
>> compilers will not help.
>> On Thu, Dec 13, 2012 at 1:25 PM, Nazim Mer <nazim.mer at gmail.com> wrote:
>> > could GPUocelot be incorporated into blender so that CUDA works on AMD
>> > gpus
>> > http://code.google.com/p/gpuocelot/
>> > _______________________________________________
>> > Bf-cycles mailing list
>> > Bf-cycles at blender.org
>> > http://lists.blender.org/mailman/listinfo/bf-cycles
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
> Bf-cycles mailing list
> Bf-cycles at blender.org
More information about the Bf-cycles