November 2014 - Wine-Devel - list.winehq.org

Re: wined3d: Add NVIDIA Geforce GT 750M to supported device list.

by Jonas Maebe

On 18/11/14 17:22, Matteo Bruni wrote: > Modifying that SM4 check is fine but we'd still require GLSL 1.50 and > that means the check is still going to fail with those drivers. In > theory we could also tone it down and e.g. only look for the SM4-level > features supported by all the drivers but I'm not sure the end result > would make a lot of sense. The main issue right now (as far as I'm concerned) is that pretty much all modern cards that are not explicitly supported by Wine will be wrongly detected on OS X and hence have their vram set to a ridiculously low amount. Maybe the wine project doesn't really care about this, but I guess at least Crossover should add a workaround. At least I'm not the only one that bumped into this issue: https://www.codeweavers.com/support/forums/general/?t=27;msg=167632#c35 Jonas

Nov. 18, 2014

Re: wined3d: Add NVIDIA Geforce GT 750M to supported device list.

by Matteo Bruni

2014-11-14 22:14 GMT+01:00 Andrei Slăvoiu <andrei.slavoiu(a)gmail.com>: > În ziua de Vin 14 Noi 2014, la 19:26:01, Jonas Maebe a scris: >> OpenGL extensions: >> GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, >> GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, > > Before GL_EXT_gpu_shader4 was used to differentiate SM3 cards from SM4. I > remember somebody said this is not enough to ensure the card is SM4 capable, > then how about GL_EXT_geometry_shader4? Both extensions are not exposed in the non-core profile by Mesa drivers, but apparently they are on OS X in both legacy and core profiles. ARB_shader_bit_encoding, though, is not exposed by OS X, so the SM4 check in shader_glsl_get_caps() fails. More importantly, Mesa and OS X only support the core profile for GL 3.2+ so GLSL 150 is not supported in the legacy contexts wined3d is using right now. I introduced that check back then and it is somewhat overzealous (e.g. GLSL version 1.50 pretty much implies EXT_gpu_shader4 and geometry shaders) but we will actually require that kind of features for D3D10 support. The way forward is to use 3.2+ core profiles and GLSL 1.50+ in wined3d instead of those missing extensions, but it's going to be a while for that. Modifying that SM4 check is fine but we'd still require GLSL 1.50 and that means the check is still going to fail with those drivers. In theory we could also tone it down and e.g. only look for the SM4-level features supported by all the drivers but I'm not sure the end result would make a lot of sense.

Nov. 18, 2014

Re: [PATCH 1/2] mshtml: Added support for IHTMLFrameBase::put_src call on detached element.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10324 Your paranoid android. === w2000pro (32 bit) === No test summary line found === wxppro (32 bit) === No test summary line found === wvistau64 (32 bit) === No test summary line found === w2008s64 (32 bit) === No test summary line found === w7u (32 bit) === No test summary line found === w8 (32 bit) === No test summary line found === wvistau64 (64 bit) === No test summary line found === w2008s64 (64 bit) === No test summary line found

Nov. 18, 2014

Re: [PATCH 5/6] ddraw/tests: Test messages on focus loss (v2).

by Henri Verbeet

On 17 November 2014 21:17, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > @@ -2291,6 +2320,18 @@ static void test_coop_level_mode_set(void) > user32_rect.left, user32_rect.top, user32_rect.right, user32_rect.bottom, > r.left, r.top, r.right, r.bottom); > > + expect_messages = exclusive_focus_loss_messages; > + SetForegroundWindow(GetDesktopWindow()); > + ok(!expect_messages->message, "Expected message %#x, but didn't receive it.\n", expect_messages->message); This fails for me on Windows: ddraw1.c:2295: Test failed: Expected message 0x46, but didn't receive it.

Nov. 18, 2014

Re: wined3d: Add NVIDIA Geforce GT 750M to supported device list.

by Jonas Maebe

On 14 Nov 2014, at 22:14, Andrei Slăvoiu wrote: > În ziua de Vin 14 Noi 2014, la 19:26:01, Jonas Maebe a scris: >> OpenGL extensions: >> GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, >> GL_EXT_gpu_program_parameters, GL_EXT_gpu_shader4, > > Before GL_EXT_gpu_shader4 was used to differentiate SM3 cards from > SM4. I > remember somebody said this is not enough to ensure the card is SM4 > capable, > then how about GL_EXT_geometry_shader4? According to http://shiben.blogspot.be/2007/01/shader-model-40-examples.html , that is indeed the case: "Now run glxinfo on xterm (linux), Run wglinfo.exe on cmd.exe, get wglinfo from http://www.cg.tuwien.ac.at/~wimmer/wglinfo/ (windows) See if you can see GL_EXT_geometry_shader4 in the clutter of text. If you can, you system is ready to compile and run SM4 codes." and "By the way, Shader Model 4.0 is also called the Direct X 10 Architecture" Jonas

Nov. 18, 2014

Re: [3/6] user32/tests: Reenable test function for WM_GETTEXT.

by Sebastian Lackner

On 18.11.2014 08:05, Marvin wrote: > Hi, > > While running your changed tests on Windows, I think I found new failures. > Being a bot and all I'm not very good at pattern recognition, so I might be > wrong, but could you please double-check? > Full results can be found at > https://testbot.winehq.org/JobDetails.pl?Key=10317 > > Your paranoid android. > > > === w2008s64 (64 bit win) === > win.c:3367: Test failed: hwnd 00000000000100F4 message 0118 > This is unrelated to my patch and seems to be a random-failure. Not present in 4/6: https://newtestbot.winehq.org/JobDetails.pl?Key=10318

Nov. 18, 2014

Re: configure: Fix detection of gnutls on Ubuntu 14.10.

by Sebastian Lackner

On 18.11.2014 07:52, Nicolas Le Cam wrote: > 2014-11-17 9:37 GMT+01:00 Sebastian Lackner <sebastian(a)fds-team.de>: >> Someone asked me to submit this, although its very Ubuntu specific. >> >> On some Ubuntu versions there only exists a package where libgnutls was renamed to libgnutls-deb0. As an effect ./configure fails to detect it properly because it compares the exact soname. >> >> http://packages.ubuntu.com/precise/amd64/libgnutls28/filelist >> http://packages.ubuntu.com/utopic/amd64/libgnutls-deb0-28/filelist >> >> --- >> configure.ac | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> >> > > Hi Sebastian, > > This also fixes libgnutls detection on Debian testing (and futur > Jessie) and derivatives. > > What about [[libgnutls\\(-deb[[0-9]]\\)\\{0,1\\}]] or > [[libgnutls\\(-[[0-9A-Za-z]]\+\\)\\{0,1\\}]] instead. > I don't think the debian specific soname will bump too often but it > could avoid the need for another patch. > The second idea would also match libgnutls-openssl. Not sure if that hurts, but so far this check only matches 'real' gnutls, and not the openssl wrapper lib.

Nov. 18, 2014

Re: [3/6] user32/tests: Reenable test function for WM_GETTEXT.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10317 Your paranoid android. === w2008s64 (64 bit win) === win.c:3367: Test failed: hwnd 00000000000100F4 message 0118

Nov. 18, 2014

Re: configure: Fix detection of gnutls on Ubuntu 14.10.

by Nicolas Le Cam

2014-11-17 9:37 GMT+01:00 Sebastian Lackner <sebastian(a)fds-team.de>: > Someone asked me to submit this, although its very Ubuntu specific. > > On some Ubuntu versions there only exists a package where libgnutls was renamed to libgnutls-deb0. As an effect ./configure fails to detect it properly because it compares the exact soname. > > http://packages.ubuntu.com/precise/amd64/libgnutls28/filelist > http://packages.ubuntu.com/utopic/amd64/libgnutls-deb0-28/filelist > > --- > configure.ac | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > Hi Sebastian, This also fixes libgnutls detection on Debian testing (and futur Jessie) and derivatives. What about [[libgnutls\\(-deb[[0-9]]\\)\\{0,1\\}]] or [[libgnutls\\(-[[0-9A-Za-z]]\+\\)\\{0,1\\}]] instead. I don't think the debian specific soname will bump too often but it could avoid the need for another patch. -- Nicolas Le Cam

Nov. 18, 2014

Re: [PATCH 4/6] d3d8/tests: Test style changes on focus loss.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10310 Your paranoid android. === w8 (32 bit device) === device.c:1181: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1226: Test failed: Reset failed, hr 0x88760868. device.c:1228: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1232: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1239: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1240: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1241: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1242: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1243: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1244: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1249: Test failed: Screen width is 640, expected 800. device.c:1250: Test failed: Screen height is 480, expected 600. device.c:1256: Test failed: Back buffer width is 640, expected 800. device.c:1258: Test failed: Back buffer height is 480, expected 600. device.c:1288: Test failed: Screen width is 640, expected 1024. device.c:1289: Test failed: Screen height is 480, expected 768. device.c:2364: Test failed: Expected message 0x46 for window 0, but didn't receive it. device.c:2369: Test failed: The focus window is active. device.c:2373: Test failed: Got unexpected hr 0. device.c:2379: Test failed: Got unexpected hr 0. device.c:2393: Test failed: Got unexpected hr 0. device.c:2523: Test failed: Expected foreground window 000501B8, got 0002004C. device.c:2899: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2903: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2926: Test failed: Failed to reset device, hr 0x88760868. device.c:2930: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2934: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2948: Test failed: Failed to set foreground window. device.c:2952: Test failed: Expected device window style 0x34cf0000, got 0x4cf0000. device.c:2956: Test failed: Expected device window extended style 0x108, got 0x100.

Nov. 17, 2014