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. On Sun, Jun 14, 2009 at 3:38 PM, Erich Hoover<[email protected]> wrote: > In an effort to come up with a (hopefully palatable) solution to a > couple of bugs I've put together the attached patch. Only the first > of the two issues is currently handled, though the patch paves the way > for the second issue. > > 1) Bug #15839: (not this title) Wine does not report the manufacturer > driver (for example, "nv4_disp.dll" for nVidia users) > 2) Wine does not always report the correct amount of video RAM (not > sure if there is a bug number for this) > > The approach handles graphics requests like this: > "manufacturer" driver --> "OS" driver (normally winex11.drv) > > Where the manufacturer driver (at present) forwards all requests to > the OS driver. Later additions could provide driver-specific code for > returning information such as the correct amount of video RAM. Also, > the manufacturer driver is skipped (reverting to the current behavior) > unless "HKEY_CURRENT_USER\Software\Wine\Drivers\ReportNativeVideoDriver" > is set to "Y". > > Note: patch makes changes to configure.ac, so cover your bases: > autoheader && autoconf && ./configure && make depend && make > > I'm particularly interested in comments related to how the driver is > selected (__wine_get_video_driver in gdi32), but all feedback is > welcome. > > Erich Hoover > [email protected] > > > >
