Not quite. It was just extrapolation.
Current situation with "ATI" type is poor enough even w/o any additional 
accelerator types. BOINC treats 2 completely different GPU types (different API 
= different GPU type) as single one - "ATI".
If stock app can solve this by app plan classes, anonymous platform app has no 
such possibility. "ATI" accelerator type does't discriminate between CAL and 
OpenCL  APIs.



Понедельник, 15 апреля 2013, 12:17 -07:00 от David Anderson 
<[email protected]>:
>I think there's a misunderstanding.
>If AMD started selling a different type of coprocessor,
>we'd treat it as a new coprocessor type, not as an ATI GPU.
>-- David
>
>On 15-Apr-2013 1:28 AM, Raistmer wrote:
>> I would like to attract BOINC devs attention to this issue described here:
>>  http://setiathome.berkeley.edu/forum_thread.php?id=71192&postid=1357117
>>
>> In short, current BOINC accelerator separation by vendor names is
>> inappropriate and already caused issues. Type of accelerator API - that's
>> what matters, not vendor name. If device supports few APIs it should be
>> listed under all supported types. But different API should mean different
>> type (it's possible/convenient to have few types for same API like in case of
>> OpenCL, but in no circumstances different APIs should share same type as in
>> the case of  "ATI" type currently).
>> _______________________________________________ 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.

_______________________________________________
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.

Reply via email to