February 2025 - Wine-GitLab

Re: [PATCH v6 0/6] MR7174: rtworkq: Fix handling of platform startup and lock counts.
by Conor McCarthy (＠cmccarthy) Feb. 18, 2025

Feb. 18, 2025

On Tue Feb 18 06:30:29 2025 +0000, Nikolay Sivov wrote: > I knew I commented on these changes before, but then I found it was > !7244. Could we merge those, or what's the plan? No problem to do that if 11 commits are ok. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7174#note_94962

1 0

[PATCH v5 0/6] MR7174: rtworkq: Fix handling of platform startup and lock counts.
by Conor McCarthy (＠cmccarthy) Feb. 18, 2025

Feb. 18, 2025

Startup and lock counts in native Windows are separate, and the lock count does not decrease when an async result is freed if the platform has been started. -- v5: rtworkq: Introduce an async result object cache. rtworkq: Introduce a platform startup count. rtworkq/tests: Test work queue. mfplat/tests: Test platform startup and lock counts. mfplat/tests: Test mixing of MF platform functions with their Rtwq equivalents. https://gitlab.winehq.org/wine/wine/-/merge_requests/7174

2 6

[PATCH v3 0/1] MR7339: ntdll: implement create_logical_proc_info on FreeBSD.
by Damjan Jovanovic (＠dj) Feb. 18, 2025

Feb. 18, 2025

Port the XML parser from dlls/ntdll/actctx.c to ASCII and use it to parse the XML returned from FreeBSD's kern.sched.topology_spec sysctl. -- v3: ntdll: implement create_logical_proc_info on FreeBSD. https://gitlab.winehq.org/wine/wine/-/merge_requests/7339

3 3

[PATCH v2 0/2] MR7342: Implement D3D11_FEATURE_D3D9_SIMPLE_INSTANCING_SUPPORT feature check.
by Zhiyi Zhang (＠zhiyi) Feb. 18, 2025

Feb. 18, 2025

For React Native. -- v2: d3d11: Implement D3D11_FEATURE_D3D9_SIMPLE_INSTANCING_SUPPORT feature check. https://gitlab.winehq.org/wine/wine/-/merge_requests/7342

2 4

[PATCH v3 0/1] MR7179: wined3d: Add some DXT format mappings in the Vulkan renderer.
by Aida Jonikienė Feb. 18, 2025

Feb. 18, 2025

This removes some texture errors when using Himavant. -- v3: wined3d: Add DXT format mappings in the Vulkan renderer. https://gitlab.winehq.org/wine/wine/-/merge_requests/7179

3 4

[PATCH v3 0/5] MR7347: ntdll: Avoid process_attach() even indirectly if loaded with `DONT_RESOLVE_DLL_REFERENCES`
by Jinoh Kang (＠iamahuman) Feb. 17, 2025

Feb. 17, 2025

This cleans up `LDR_DONT_RESOLVE_REFS` checks in preparation for !7. -- v3: ntdlll: Remove redundant LDR_DONT_RESOLVE_REFS checks before calling process_attach(). ntdll: Skip DLL initialization and ldr notification entirely if DONT_RESOLVE_DLL_REFERENCES is set. kernel32/tests: Test for unexpected loader notification for import dependency loaded with DONT_RESOLVE_DLL_REFERENCES. kernel32/tests: Test for unexpected LDR_PROCESS_ATTACHED flag in import dependency loaded with DONT_RESOLVE_DLL_REFERENCES. kernel32/tests: Add basic tests for internal flags of modules loaded with DONT_RESOLVE_DLL_REFERENCES. https://gitlab.winehq.org/wine/wine/-/merge_requests/7347

2 6

[PATCH 0/5] MR4894: setupapi: implement CM_Locate_DevNode
by Etaash Mathamsetty (＠etaash.mathamsetty) Feb. 17, 2025

Feb. 17, 2025

This api is used by libxess on intel GPUs. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4894

3 8

Re: [PATCH v8 0/2] MR7060: scrrun/tests: Add drive_get_path test
by Quinn Rafferty (＠ramleejo) Feb. 17, 2025

Feb. 17, 2025

On Wed Jan 1 16:32:32 2025 +0000, Nikolay Sivov wrote: > @alexhenrie is it possible to create a drive without a letter? Regarding > wine supporting only drives with assigned letters, I don't think it > matters that much if it turns out to be easy to return a correct path. > IDrive has separate properties for paths and letters, so maybe there is > a reason for that. My understanding is that the way to query all available drives is via DriveCollection. Due to this I changed the tests to what Alex Henrie suggested as it will properly verify the functionality of the function. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7060#note_94929

1 0

[PATCH v4 0/2] MR7238: winebus,mmdevapi: implement audio device container id
by Harald Sitter (＠sitter) Feb. 17, 2025

Feb. 17, 2025

This is a bit convoluted because of the amount of pieces involved. I'll try to untangle things a bit. The container id is meant to be globally unique and stable. We therefore need a suitable amount of stable entropy that we can feed into a hash function to get a stable and unique output. This happens in winebus. The corner stone of hash inputs is the linux device topology (sysfs path) obtained via udev. Along with all other possible data we feed this into a hash function to obtain our container id. A bunch of extra wine-specific keys needed to be added to carry the necessary metadata from the driver into the ntoskrnl (where it gets written to the property registry of the relevant device). Separate from this we also ingest the linux device topology (sysfs path) in the winepulse driver. In mmdevapi we then use winepulse's sysfs path to find the matching device in the setupapi and query its container id. We now have the same container id in both the device and the MMDevice, allowing applications (in particular Games) to find the MMDevice for a given device. For practical reasons we always resolve the sysfs path to the root device as early as possible. Container ids are meant to be equal for sub devices inside a "container" anyway. -- v4: containerid: helper to generate a containerid from a sysfs path mmdevapi: correctly read and write containerid as clsid blob https://gitlab.winehq.org/wine/wine/-/merge_requests/7238

2 3

Re: [PATCH v3 0/2] MR7341: shdocvw: Remove two functions. - approved
by Alexandre Julliard (＠julliard) Feb. 17, 2025

Feb. 17, 2025

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7341

1 0