Request for comments on patch

[Roderick Colenbrander]

On Sun, Jun 14, 2009 at 10:45 PM, Erich Hoover<ehoover at mines.edu> wrote:
> On Sun, Jun 14, 2009 at 2:26 PM, Mike
> Kaplinskiy<mike.kaplinskiy at gmail.com> wrote:
>> I don't know about stubbing drivers, but I remember that
>> autodetection/registry wasn't accepted on the fallout 3 patch. I think
>> AJ would prefer something like
>> http://source.winehq.org/git/wine.git/?a=commit;h=f2e2e3e49947490368900ef06a92e1df1bc52820
>> but for driver dll strings.
>>
>> But take my comments with a grain of salt. I just watch the list most
>> of the time and don't really understand the graphics stuff too well.
>>
>> Mike.
>>
>
> It's been some time since I've seen those patches pass through (it's
> also possible I missed the patch your talking about), but if I
> remember correctly there were a couple different reasons they were
> rejected.  It sounded like the issue was that they reported a driver
> that doesn't exist and/or that the registry key manually specified a
> driver.  My suggestion is that there's a "try to report the
> manufacturer driver" type registry key and that it, when activated,
> reports a real driver.  This real driver then funnels the requests
> back to winex11.drv (with room to add additional non-funneled requests
> later, such as requesting the card's video RAM).
>
> Erich Hoover
> ehoover at mines.edu
>
>
>

The only thing I didn't add yet was driver identification as I didn't
have time for it yet but I just plan to add that to a table in wined3d
(the reported driver name depends also on the windows version). In the
end adding such info to the display driver would make sense though but
I don't think it brings us much at this point.

Roderick