GPU driver version reporting

[Roderick Colenbrander]

On Wed, Jun 2, 2010 at 5:20 AM, Albert Lee <trisk at forkgnu.org> wrote:
> On Wed, 2 Jun 2010 03:14:34 +0000, Seth Shelnutt <shelnutt2 at gmail.com>
> wrote:
>> I am trying to get folding at home gpu client working. The issue we are
>> having now is that it detects the driver version and says it is not
>> right, and it won't proceed. I've searched through the lines of a
>> WINEDEBUG=+trace and I think the issue is:
>>
>> 0009:trace:d3d:init_driver_info OS version 5.1.
>> 0009:trace:d3d_caps:init_driver_info Found card 10de:05e2 in driver DB.
>> 0009:trace:d3d_caps:init_driver_info Reporting (fake) driver version
>> 0x0006000f-0x000b21aa.
>>
>> It could also be from:
>> 0009:trace:reg:NtSetValueKey (0x14,L"Driver",1,0xff883b94,20)
>> 0009: set_key_value( hkey=0014, type=1, namelen=12, name=L"Driver",
>> data={57,00,49,00,4e,00,45,00,20,00,53,00,43,00,53,00,49,00,00,00} )
>>
>> But I think that is just trying to set a registry key, not get a
> registry
>> key (i.e. the driver version from the registry).
>>
>> What I can't figure out is what version this is reporting. I've searched
>> but I can't find this driver DB, so I don't know what
>> 0x0006000f-0x000b21aa corespondent too. Can someone point me in the
> right
>> directions?
>>
>> Thanks,
>>
>> Seth Shelnutt
>
> It's a table at:
> http://source.winehq.org/source/dlls/wined3d/directx.c#L983
>

Sure the code is in directx.c but the I suspect the issue Seth is
seeing is that different parts of Wine expose different version
numbers. Some games also have this issue (I believe they use some
user32 code which just returns the display driver name reported by
winex11.drv which is different from what wined3d mentions). It can be
that real windows also stores it somewhere in the registry which we
don't.

Roderick