Thanks for reporting it. I have asked relevant people about it.
Still waiting for some infos;
If you "open" the current AMD OpenCL ICD (amdocl.dll, Ver: 10.0.1124.2) you will find this:
Select the turks processor
Select the trinity processor
Select the tahiti processor
Select the slimer processor
Select the rv770 processor
Select the rv730 processor
Select the rv710 processor
Select the redwood processor
Select the pitcairn processor
Select the owls processor
Select the oland processor
Select the kauai processor
Select the kalindi processor
Select the juniper processor
Select the hawk processor
Select the hainan processor
Select the finch processor
Select the eagle processor
Select the cypress processor
Select the crow processor
Select the cedar processor
Select the cayman processor
Select the casper processor
Select the capeverde processor
Select the caicos processor
Select the bonaire processor
Select the barts processor
The RED marked OpenCL "targets" are "new" or unknown .. if we count them into CAL, there are more than 30 CALtargetIDs at the moment, but only 19 are documented (nonNDA)
The ORANGE marked OpenCL "targets" are new but aviable (or aviable soon)
Q1: Could AMD release a current list with GPU, CaltargetID & OpenCL-Names
Q2: What are those birds-GPUs (Crow, Hawk, Eagle ....)
Q3: What are those ghosts-GPUs (Casper & Slimer) ?
AMD should do more "support" and give more infos - look at the outdated plattform infos at http://support.amd.com/us/Pages/techdocs.aspx-:
- no updated Family 15h Model 10h-1Fh infos about Richland
- no Family 16h Model 00h-0Fh infos (Rev Guide, BKDG ..) only SOG
1 of 1 people found this helpful
This had been discussed internally. The AMD OpenCL Programming Guide will be updated accordingly. I will also post the enum here, if i get the permission.
1 Month and no answer ....
There is no "secret"/NDA about released protducts so AMD give informations to us.
Even if its only:
CAL_TARGET_600 = 0, /**< R600 GPU ISA */
CAL_TARGET_610 = 1, /**< RV610 GPU ISA */
CAL_TARGET_630 = 2, /**< RV630 GPU ISA */
CAL_TARGET_670 = 3, /**< RV670 GPU ISA */
CAL_TARGET_7XX = 4, /**< R700 class GPU ISA */
CAL_TARGET_770 = 5, /**< RV770 GPU ISA */
CAL_TARGET_710 = 6, /**< RV710 GPU ISA */
CAL_TARGET_730 = 7, /**< RV730 GPU ISA */
CAL_TARGET_CYPRESS = 8, /**< CYPRESS GPU ISA */
CAL_TARGET_JUNIPER = 9, /**< JUNIPER GPU ISA */
CAL_TARGET_REDWOOD = 10, /**< REDWOOD GPU ISA */
CAL_TARGET_CEDAR= 11, /**< CEDAR GPU ISA */
CAL_TARGET_SUMO = 12, /**< SUMO GPU ISA */
CAL_TARGET_SUPERSUMO =13, /**< SUPERSUMO GPU ISA */
CAL_TARGET_WRESTLER = 14, /**< WRESTLER GPU ISA */
CAL_TARGET_CAYMAN =15, /**< CAYMAN GPU ISA */
CAL_TARGET_KAUAI = 16, /**< KAUAI GPU ISA */
CAL_TARGET_BARTS = 17 , /**< BARTS GPU ISA */
CAL_TARGET_TURKS = 18 , /**< TURKS GPU ISA */
CAL_TARGET_CAICOS = 19, /**< CAICOS GPU ISA */
CAL_TARGET_TAHITI = 20,
CAL_TARGET_PITCAIRN = 21,
CAL_TARGET_CAPEVERDE = 22,
CAL_TARGET_TRINITY = 23,
CAL_TARGET_RESERVED24 = 24,
CAL_TARGET_RESERVED25 = 25,
CAL_TARGET_BONAIRE = 26,
CAL_TARGET_RESERVED27 = 27,
Please wait for the next SDK release which shall happen some time in near future . The enum will be updated in the programming guide.
Still waiting ?!
It would be very nice if AMD could confirm the CAL-target-IDs of released products as part of the "normal" product & developer support !
That would be Oland GPU, Trinity/Richland APU, Kabini/Temash APU, Hainan GPU ....
20 : Tahiti
21 : Pitcairn
22 : Capeverde
23 : Devastator (Trinity/Richland)
24 : Scrapper (Trinity/Richland)
25 : Oland
26 : Bonaire
27 : Casper
28 : Slimer
29 : Kalindi (Kabini/Temash)
30 : Hainan
31 : Curacao
The enum list has been updated in the Programming Guide. New Programming Guide will be released along with AMD APP SDK, quite soon.
Anyways your guesses are appropriate.
Excuse me, but why are CAL target id's are important nowadays?
As I know for the 7970 hardware CAL API (not CAL itself inside the driver) is dead since cat12.4. I had a bug back then, that I was only able to write data into the CB, not the UAV... lol.
Or is the CAL api working again?
1st - CAL isnt dead - still there inside Catalyst 13.6 for Windows NT 6.0 or newer (removed from NT 5.1 & 5.2) and is working!
2nd - some programs run faster with CAL instead of OpenCL because OpenCL mostly need 1 free CPU-Core/Thread; CAL only need 0,05 - bad for Boinc & Co.!
3rd - AMDs OpenCL ICD is build on top of CAL! - if you remove the CAL-APIs - the GPU-Part of the OpenCL ICD wont work!
4th - you need to identify the GPU you wanna run the programm (for tweaking, codepaths ...)
5th - Collatz CAL runs on both GPUs of an AMD Radeon HD 5970 ; OpenCLprograms have problems with 2nd GPU of the 5970