search

austinulmer / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Adding NvAPI_GPU_GetPCIIdentifiers(NvPhysicalGpuHandle hPhysicalGpu,NvU32 *pDeviceId,NvU32 *pSubSystemId,NvU32 *pRevisionId,NvU32 *pExtDeviceId) #209

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
To the NvidiaGPU report. I need the pciID's of detected hardware, I could 
probably edit it in the code myself but then I would need to constantly keep 
editing it in every new revision.

I'll probably edit it in myself for now and wait until/if you release a version 
with this feature built in as I really need that ID from ohmlib.

I was 90% done with a total vb.net conversion of the library, enabling me to 
add things easily myself, until I noticed the interfaces now giving me all info 
I need ( except this ), thanks for your continued work on this great project!

Original issue reported on code.google.com by mtm78.cf...@gmail.com on 5 May 2011 at 7:07

GoogleCodeExporter commented 9 years ago 
It would be even nicer if the nvapi section of the report would contain the 
same info about active/present outputs, sli status maybe even ect. My c# is bad 
to say the least and I failed to edit the api call's in, and I stopped with 
converting the library to vb since the interfaces are now very good ( though it 
would be nice if the report function of nvidia and ati gpu's would return 
either the whole adl/nvapi section, or even nicer just the section about that 
particular gpu.. ) but I'm asking allot I think so I don't mind if you mark it 
low priority or even irrelevant to extend the functionality of the library much 
beyond the use of openhardwaremonitor itself ( though one can always hope ;) ).

Original comment by mtm78.cf...@gmail.com on 8 May 2011 at 10:43

GoogleCodeExporter commented 9 years ago 
Even if they are windows specific could the values from strDriverPath and 
strDriverPathExt be added to the ADL report as well? I am using registry calls 
to id the driver version since the adl lib doesn't seem to report it?

Proposed changes below

report.Append("strDriverPath: ");
report.AppendLine(adapterInfo[i].DriverPath.ToString(CultureInfo.InvariantCultur
e));
report.Append("strDriverPathEX: ");
report.AppendLine(adapterInfo[i].DriverPathExt 
.ToString(CultureInfo.InvariantCulture ));

Original comment by mtm78.cf...@gmail.com on 9 May 2011 at 12:00

GoogleCodeExporter commented 9 years ago 
'The ATIAGSDriverGetVersionInfo() function enables developers to query the 
currently installed version of ATI graphics drivers. The returned structure 
contains two strings: the first refers to the build id of the graphics driver 
package (“8.723-100406a-098769C-ATI” is returned for Catalyst 10.4 for 
example), and the second contains the public release id (“10.4” is returned 
for Catalyst 10.4 for example).'

source -> follow from here ( AGS ) 
http://developer.amd.com/gpu/ags/Pages/default.aspx

I'll have to add them myself if I want to avoid the registry.

Original comment by mtm78.cf...@gmail.com on 9 May 2011 at 12:17

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r372.

Original comment by moel.mich on 15 Jan 2012 at 3:35