- 28 Mar, 2022 4 commits
-
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <zfigura@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
- 25 Mar, 2022 33 commits
-
-
Alexandre Julliard authored
Signed-off-by: -
Eric Pouech authored
Also add fallback method when legacy console APIs where used. Signed-off-by:
Eric Pouech <eric.pouech@gmail.com> Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Eric Pouech authored
Signed-off-by:
-
Jinoh Kang authored
The 'status' field of send_socket_request is always either STATUS_PENDING or STATUS_DEVICE_NOT_READY, and the 'total' field is always zero. Replace the 'status' field with 'force_async' boolean field, and get rid of the 'total' field entirely. Also, clean up the send_socket handler code a bit. Signed-off-by:
Jinoh Kang <jinoh.kang.kr@gmail.com> Signed-off-by:
-
Jinoh Kang authored
Otherwise, try_send() call from sock_send() may race against try_send() call from async_send_proc(), shuffling the packet order. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52401Signed-off-by:
-
Jinoh Kang authored
If the type of the socket is SOCK_DGRAM, it shall always be bound to an address if we ever attempt to send datagrams through the socket, whether the attempt succeeds or not. Signed-off-by:
-
Jinoh Kang authored
Make send_socket alert the async immediately if poll() call detects that there are incoming data in the socket, bypassing the wineserver's main polling loop. For sock_transmit, we always mark the async as pending and set the IOSB (unless async allocation has failed). Signed-off-by:
-
Jinoh Kang authored
This allows the initial I/O to be performed after the send_socket handler is called. Signed-off-by:
-
Jinoh Kang authored
This also makes async_handoff() behaviour more consistent with async_set_result() for handling I/O failures. Signed-off-by:
-
Jinoh Kang authored
Today, async_set_completion_callback() is used to register a function that is called when the async I/O is completed. It is assumed that the async will eventually be queued when such callback is registered. However, this incurs extra complexity in future code that needs the completion logic to be invoked even if the async is never actually queued (e.g. when the I/O failed synchronously before async_handoff). Generalise async completion callback by calling it in async_handoff() when the I/O status indicates failure. Signed-off-by:
-
Hans Leidekker authored
Signed-off-by:
Hans Leidekker <hans@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Huw Davies authored
Mainly to avoid a clang warning. Signed-off-by:
Huw Davies <huw@codeweavers.com> Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com> Signed-off-by:
-
Gabriel Ivăncescu authored
According to the ES6 spec, it should work in generic way for objects exposing "source" and "flags", but native IE seems to not follow it here and throws. Signed-off-by:
-
Gabriel Ivăncescu authored
According to the ES6 spec, they don't throw anymore (compared to ES5), but native IE seems to not follow it here and throws anyway. Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
-
Gabriel Ivăncescu authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Francois Gouget authored
Signed-off-by:
Francois Gouget <fgouget@free.fr> Signed-off-by:
-
Paul Gofman authored
Signed-off-by:
Paul Gofman <pgofman@codeweavers.com> Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Jan Sikorski authored
Avoids needing to fault-in the memory on each recording. Signed-off-by:
Jan Sikorski <jsikorski@codeweavers.com> Signed-off-by:
-
Huw Davies authored
Signed-off-by:
Andrew Eikum <aeikum@codeweavers.com> Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
This means the thread doesn't have to wake every 250ms to test "end_thread". Signed-off-by:
-
Huw Davies authored
Signed-off-by:
-
Huw Davies authored
The motivation is that this will need to be called from a non-Win32 thread and so shouldn't use the Win32 API. An added benefit is that it will eliminate the 16ms jitter associated with GetTickCount(). Signed-off-by:
-
Alexandre Julliard authored
Similar to what AC_PROC_CC does for the host compiler. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52723Signed-off-by:
-
- 24 Mar, 2022 3 commits
-
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Win7 has spurious device arrival / removal messages for the first polled HID device created, probably when installing the driver the first time, and it causes a timeout if we open it before it completed its sequence. Signed-off-by:
-
Huw Davies authored
The MIM_DATA and MIM_LONGDATA notifications are sent via the notification thread. The midi_handle_event syscall is temporary. Signed-off-by:
-
