- Wine-GitLab - list.winehq.org

Re: [PATCH v2 0/1] MR8683: msado15/tests: Fixup error return values for the ConnectionPoint tests. - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

[PATCH 0/1] MR8667: winebus.sys: VID 3344 devices now are catch-all hidraw for compatability.
by Ty (＠chaos) July 31, 2025

July 31, 2025

_**Summary:**_ - changes hidraw handling for VID 3344 devices to a catch-all, ensuring the multitude (36+ devices) of virpil(vpc) devices with nearly infinitely variable parameters are all supported. _**Reason for code departing existing standards:**_ - Virpil (vpc) devices all require hidraw, vpc has never expressed interest in making a device that does not, and the devices have user defined: button counts (0-128), axis counts (0-8), PID (mandatory for user to change in case of twin-stick or twin control panels), and device descriptions. default PID is dependant on revision of device or first-firmware-installed. Because of how custom each users device is, indexing them from anything apart from VID will inherently miss some(often many) devices, breaking support. - Unfortunately, the cat is well and truly out of the bag already for virpil, so fixing the PID issues by way of virpil releasing firmware changes is not practical (forcing PID changes from virpil would reset keybinds for ~10k-100k windows and linux users in many of their games). _**Possible (theoretical) flaw with the approach:**_ - Leaguer Microelectronics (LME) shares a VID with Virpil (VPC). If any devices exist outside of virpil (say, a bootleg xinput controller off aliexpress that chose a random vid and landed on 3344), they may be adversely affected and need explicit exemption else the end user would need to set them similarly to how virpil users need to modify their kit today. LME is primarily an IoT company so should not cause any issues, but it is possible. similarly, if VPC ever released a gamepad controller (xinput) it would also have issues. VPC has never expressed interest in doing this however, so this fix should be safe forever for VPC. LME being IoT should be fairly safe, but it is something to watch for. _**The fix for the theoretical flaw:**_ - should this show up as a real issue, explicit exemption from this catch-all via an if-else or switch statement for adversely affected devices should be done. _**Closing:**_ - If there are any questions / comments, I am happy to discuss it. After long thought, ~2 years of talk on proton issues, this seems to be the logical best solution for a fix given the specific situation. In the interest of keeping this some-what light reading for a laughably small code change, I will spare the minutia of the technical details for the hardware. Hopefully this merge request should provide adequate information to any maintainer looking at why this code is the way it is, some decade down the line. Have a nice day. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8667

3 5

[PATCH v3 0/4] MR8555: windows.devices.enumeration: Reimplement DeviceInformationStatics::FindAllAsync and DeviceWatcher using the device query API.
by Vibhav Pant (＠vibhavp) July 31, 2025

July 31, 2025

Implement `DeviceWatcher` on top of a `HDEVQUERY` object, obtained from `DevCreateObjectQuery`. All events from the query object's associated callback are directly forwarded to the `DeviceWatcher`'s corresponding event handlers. As closing/freeing the `HDEVQUERY` is performed asynchronously, I have also added `IWeakReference` support for the device watcher. -- v3: windows.devices.enumeration: Implement DeviceInformationStatics::DeviceWatcher using DevCreateObjectQuery. windows.devices.enumeration: Implement IWeakReferenceSource for DeviceWatcher. windows.devices.enumeration/tests: Add weak reference tests for DeviceWatcher. https://gitlab.winehq.org/wine/wine/-/merge_requests/8555

2 7

Re: [PATCH v4 0/5] MR8681: widl: Require runtimeclass contract or version attribute. - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

Re: [PATCH v2 0/1] MR8682: winebus.sys: Prefer hidraw for all Virpil (VID 3344) devices. - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

Re: [PATCH v2 0/1] MR8680: winebus.sys: Fix DualSense BT quirk. - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

Re: [PATCH v3 0/2] MR8662: Revert "mmdevapi: Error out if the channel count or sampling rate doesn't match the mix format." - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

Re: [PATCH v2 0/3] MR8674: win32u: Update DC OpenGL drawable when it is acquired. - approved
by Alexandre Julliard (＠julliard) July 31, 2025

July 31, 2025

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

1 0

[PATCH v10 0/5] MR8564: cfgmgr32: Device query API part 3: Implement DevGetObjectProperties(Ex) and HDEVQUERY device updates.
by Vibhav Pant (＠vibhavp) July 31, 2025

July 31, 2025

-- v10: cfgmgr32: Implement device updates for DevCreateObjectQuery. ntoskrnl.exe/tests: Add tests for device updates in DevCreateObjectQuery. cfgmgr32: Implement DevGetObjectProperties for device interfaces. cfgmgr32: Implement DevFreeObjectProperties. https://gitlab.winehq.org/wine/wine/-/merge_requests/8564

3 6

[PATCH v2 0/2] MR8555: windows.devices.enumeration: Reimplement DeviceInformationStatics::FindAllAsync and DeviceWatcher using the device query API.
by Vibhav Pant (＠vibhavp) July 31, 2025

July 31, 2025

Implement `DeviceWatcher` on top of a `HDEVQUERY` object, obtained from `DevCreateObjectQuery`. All events from the query object's associated callback are directly forwarded to the `DeviceWatcher`'s corresponding event handlers. As closing/freeing the `HDEVQUERY` is performed asynchronously, I have also added `IWeakReference` support for the device watcher. -- v2: windows.devices.enumeration: Implement DeviceInformationStatics::DeviceWatcher using DevCreateObjectQuery. https://gitlab.winehq.org/wine/wine/-/merge_requests/8555

3 12