- 06 Sep, 2021 13 commits
-
-
Zhiyi Zhang authored
Signed-off-by:
Zhiyi Zhang <zzhang@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Zhiyi Zhang authored
Signed-off-by:
-
Zhiyi Zhang authored
Signed-off-by:
-
Alex Henrie authored
The code that used it was removed in commit 8ac77cfb. Signed-off-by:
Alex Henrie <alexhenrie24@gmail.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <zfigura@codeweavers.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Francois Gouget authored
Signed-off-by:
Francois Gouget <fgouget@free.fr> Signed-off-by:
Piotr Caban <piotr@codeweavers.com> Signed-off-by:
-
Francois Gouget authored
Signed-off-by:
-
Esme Povirk authored
Signed-off-by:
Esme Povirk <esme@codeweavers.com> Signed-off-by:
-
Alex Henrie authored
Signed-off-by:
-
Alexandre Julliard authored
Put them all at the same level, like recent Windows versions do. Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by:
-
- 03 Sep, 2021 27 commits
-
-
Francois Gouget authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Instead of manually specifying success or failure. Based on test_return_status() in ntoskrnl. The changes in this patch don't affect device IRPs, but the tests show the heuristic that Windows uses, and in practice it turns out to be correct for all known asyncs. Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
server: Use a separate function and flag to communicate that the initial status of an async is not known yet. Mostly just to simplify the interface, so that we don't need to use the return value to communicate this. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
Devices are only added from a single thread but they may be destroyed concurrently so we need to guard the list against race conditions. Signed-off-by:
-
Rémi Bernon authored
And name the callbacks a bit more consistently. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
This internal xinput PDO is an HID compatible pass-through device, but it needs to be kept private and is listed on the internal WINEXINPUT device interface class, instead of the HID device interface class. This is a Wine extension for convenience and native XInput driver uses a different, undocumented, device interface. We now filter the report read requests to make sure only one is sent through to the lower bus device, and we complete both gamepad and xinput read requests at once using the returned data. Signed-off-by:
-
Rémi Bernon authored
Although these devices will be HID compatible we need to not have them listed on the HID class, as they should only be used internally by Wine XInput implementation. Signed-off-by:
-
Rémi Bernon authored
So everything will be ready in the device fdo (or fail to start the device entirely), when we need it later. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
