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

Re: Serial port sniffing problem

by Christopher Harrington

On Tue, Nov 29, 2016 at 1:22 AM Bill Lionheart <billlionheart(a)gmail.com> wrote: > Using Wine version 1.8 on Ubuntu 14.04.5 > I'm trying to use a AVRT5 APRS amateur radio GPRS tracker which has a > serial interface. The device is supplied with a Prolific USB serial > converter which comes up as /dev/ttyUSB0 which > I have sym linked to COM1 > Can you please cd into your dosdevices folder and run this command? ls -Fl (that's an uppercase F and a lowercase L) Then we will also need to see permissions of the serial device, so run this: ls -l /dev/ttyUSB0 That's a lowercase L again... and run this too: id -a With all this info we can rule out a couple problems, chief among them: 1. Is the symlink named correctly and actually pointing to something that exists 2. Do you actually have permissions to access the serial port If you provide the output of all three of these commands, we should be able to help. -Chris > >

Nov. 29, 2016

Re: [PATCH v2] ws2_32/tests: Add IDN resolution tests for GetAddrInfoW

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=26981 Your paranoid android. === w7u (32 bit sock) === sock.c:8270: Test failed: Overlapped TransmitFile failed. sock.c:8272: Test failed: Overlapped TransmitFile sent an unexpected number of bytes (219 != 209).

Nov. 29, 2016

Re: [PATCH 9/9] d3d11/tests: Add test for typed UAV loads.

by Józef Kucia

On Tue, Nov 29, 2016 at 4:16 PM, Henri Verbeet <hverbeet(a)gmail.com> wrote: > On 29 November 2016 at 12:06, Józef Kucia <jkucia(a)codeweavers.com> wrote: >> Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> >> --- >> dlls/d3d11/tests/d3d11.c | 326 +++++++++++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 326 insertions(+) >> > This fails for me on Windows: > > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (0, 0). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (1, 0). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (2, 0). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (3, 0). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (0, 1). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (1, 1). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (2, 1). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (3, 1). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (0, 2). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (1, 2). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (2, 2). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (3, 2). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (0, 3). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (1, 3). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (2, 3). > d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected > 0x00000000 at (3, 3). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (0, 0). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (1, 0). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (2, 0). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (3, 0). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (0, 1). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (1, 1). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (2, 1). > d3d11.c:11568: Test failed: Test 5: Got 0x00000010, expected > 0x00000000 at (3, 1). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (0, 2). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (1, 2). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (2, 2). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (3, 2). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (0, 3). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (1, 3). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (2, 3). > d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected > 0x00000000 at (3, 3). > > FWIW, this runs fine on Windows 10 with ATI and Intel GPU. The failures are for reading from a UAV register which has no UAV.

Nov. 29, 2016

Re: [PATCH 4/5] d3d11/tests: Add test for shader input register limits.

by Józef Kucia

On Tue, Nov 29, 2016 at 3:26 PM, Henri Verbeet <hverbeet(a)gmail.com> wrote: > On 28 November 2016 at 23:19, Józef Kucia <joseph.kucia(a)gmail.com> wrote: >> That's bad. Generally, SM4 hardware is expected to support 32 >> samplers. > Are you sure about that? The actual hardware limit seems to be 18, and > D3D11_COMMONSHADER_SAMPLER_SLOT_COUNT is 16 as well. The sampler register limit even for SM5 is 16, obviously. My memory doesn't suit me well ;-) > The hardware texture resource limit is much higher at 176, but that > doesn't help much in OpenGL unless you use something like > ARB_bindless_texture. Yeah, I was thinking that this issue starts after 32nd GL sampler.

Nov. 29, 2016

Re: [PATCH 9/9] d3d11/tests: Add test for typed UAV loads.

by Henri Verbeet

On 29 November 2016 at 12:06, Józef Kucia <jkucia(a)codeweavers.com> wrote: > Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> > --- > dlls/d3d11/tests/d3d11.c | 326 +++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 326 insertions(+) > This fails for me on Windows: d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (0, 0). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (1, 0). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (2, 0). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (3, 0). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (0, 1). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (1, 1). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (2, 1). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (3, 1). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (0, 2). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (1, 2). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (2, 2). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (3, 2). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (0, 3). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (1, 3). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (2, 3). d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected 0x00000000 at (3, 3). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (0, 0). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (1, 0). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (2, 0). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (3, 0). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (0, 1). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (1, 1). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (2, 1). d3d11.c:11568: Test failed: Test 5: Got 0x00000010, expected 0x00000000 at (3, 1). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (0, 2). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (1, 2). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (2, 2). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (3, 2). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (0, 3). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (1, 3). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (2, 3). d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected 0x00000000 at (3, 3).

Nov. 29, 2016

Re: [PATCH] ws2_32/tests: Add IDN resolution test for GetAddrInfoW

by Bruno Jesus

On Tue, Nov 29, 2016 at 12:10 PM, Alexandre Julliard <julliard(a)winehq.org> wrote: > Bruno Jesus <00cpxxx(a)gmail.com> writes: > >> I'm using €.linux.it because I could not find any standard domain name >> for validation. Maybe winehq.org could have a IDN sub-domain name to >> test. > > I created テスト.winehq.org for this purpose. Thanks, I have updated the tests but testbot VMs are not resolving it yet, so I didn't send the patch yet. >> Also instead of broken'ing every test to catch Windows <= 7 I'm >> skipping before, so real failures are not lost due to broken covering >> them in Win >= 8. > > I still think it's better to avoid version checks. You can do broken() > on the first test and skip the others if you detect the Win 7 behavior. Ok, no problem. Best wishes, Bruno

Nov. 29, 2016

Re: [PATCH 4/5] d3d11/tests: Add test for shader input register limits.

by Henri Verbeet

On 28 November 2016 at 23:19, Józef Kucia <joseph.kucia(a)gmail.com> wrote: > That's bad. Generally, SM4 hardware is expected to support 32 > samplers. Are you sure about that? The actual hardware limit seems to be 18, and D3D11_COMMONSHADER_SAMPLER_SLOT_COUNT is 16 as well. The hardware texture resource limit is much higher at 176, but that doesn't help much in OpenGL unless you use something like ARB_bindless_texture.

Nov. 29, 2016

Re: [PATCH] ws2_32/tests: Add IDN resolution test for GetAddrInfoW

by Alexandre Julliard

Bruno Jesus <00cpxxx(a)gmail.com> writes: > I'm using €.linux.it because I could not find any standard domain name > for validation. Maybe winehq.org could have a IDN sub-domain name to > test. I created テスト.winehq.org for this purpose. > Also instead of broken'ing every test to catch Windows <= 7 I'm > skipping before, so real failures are not lost due to broken covering > them in Win >= 8. I still think it's better to avoid version checks. You can do broken() on the first test and skip the others if you detect the Win 7 behavior. -- Alexandre Julliard julliard(a)winehq.org

Nov. 29, 2016

Re: shell32/tests: Add some uuids present on Windows 10.

by Huw Davies

On 29 Nov 2016, at 13:54, Nikolay Sivov <bunglehead(a)gmail.com> wrote: > > On 29.11.2016 16:43, Huw Davies wrote: > >> +DEFINE_GUID(IID_UnknownInterface22, 0x42f85136, 0xdb7e, 0x439c, 0x85,0xf1, 0xe4,0x07,0x5d,0x13,0x5f,0xc8); > > This one is IID_IFileDialog. Ah yes, thanks. Not sure how I messed up my grep to miss that. Sent v2. Huw.

Nov. 29, 2016

Re: shell32/tests: Add some uuids present on Windows 10.

by Nikolay Sivov

On 29.11.2016 16:43, Huw Davies wrote: > +DEFINE_GUID(IID_UnknownInterface22, 0x42f85136, 0xdb7e, 0x439c, 0x85,0xf1, 0xe4,0x07,0x5d,0x13,0x5f,0xc8); This one is IID_IFileDialog.

Nov. 29, 2016