cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

tt_sd349f
Journeyman III

Get_Display_DisplayInfo_Get() failed

Jump to solution

I use it to get all the displays' information like this:

int displayCount = 0;

LPADLDisplayInfo displaysInfo = NULL;

ADL_Main_Memory_Free((void**)&displaysInfo);

int ret = ADL_Display_DisplayInfo_Get(-1, &displayCount, &displaysInfo, 0);

But it failed and return -5. I checked it in the ADL_SDK_4.0, it should mean "Invalid ADL index passed".

And the API's detail description told me the first parameter could be -1 in order to retrieve all displays' information.

The text reads as follows:

[in]  iAdapterIndex     The ADL index handle of the desired adapter. A value of -1 returns all displays in the system across multiple GPUs.

How could I use this API to retrieve all displays' information?

0 Likes
1 Solution

Accepted Solutions
iblank
Staff
Staff

Re: Get_Display_DisplayInfo_Get() failed

Jump to solution

Unfortunately the help is misleading.  “ADL_Display_DisplayInfo_Get” ADL call does not support -1 value for
adapter index. You will have to call the function multiple times passing individual and valid adapter indexes to get list of all display info in the system.  The ADL_Sample project from the SDK demonstrates how to get list of adapters and how to get list of displays for each adapter.

View solution in original post

0 Likes
2 Replies
iblank
Staff
Staff

Re: Get_Display_DisplayInfo_Get() failed

Jump to solution

Unfortunately the help is misleading.  “ADL_Display_DisplayInfo_Get” ADL call does not support -1 value for
adapter index. You will have to call the function multiple times passing individual and valid adapter indexes to get list of all display info in the system.  The ADL_Sample project from the SDK demonstrates how to get list of adapters and how to get list of displays for each adapter.

View solution in original post

0 Likes
tt_sd349f
Journeyman III

Re: Get_Display_DisplayInfo_Get() failed

Jump to solution

thanks for your reply!

0 Likes