Well, yes, OpenCL is just language. And "ATI" is just name of one of brands (dead brand, btw). That is, "ati13ati" equally inadequate to describe hardware abilities as "OpenCL".
W/o introducing new plan class how do you propose to tell BOINC that it can summon particular app for one of AMD devices and can't for another one? We have 2 devices with different capabilities, no matter that they belong to same hardware brand, brand label means nothing in this case, hardware capabilities are matters! ----- Original Message ----- From: David Anderson To: [email protected] Sent: Monday, March 14, 2011 7:29 PM Subject: Re: [boinc_dev] OpenCL plan class On 14-Mar-2011 2:37 AM, Richard Haselgrove wrote: > > The issue is not really one of plan_classes, but of whether the construct > > <coproc> > <type>OpenCL</type> > </coproc> > > is recognised by the client: no, it isn't, according to coproc_detect.cpp Nor should it be; OpenCL is a language system, not a GPU type. -- David _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
