------------------ Original ------------------
Date: Thu, Jan 7, 2016 10:49 PM
To: "fracting"<fracting@gmail.com>; "Sebastian Lackner"<sebastian@fds-team.de>;
Cc: "wine-devel"<wine-devel@winehq.org>; "刘昌辉"<liuchanghui@linuxdeepin.com>;
Subject: Re: hidclass.sys: Properly quit hid_device_thread when bothcompletion event and halt event are signaled (try 2)
On 1/7/16 12:47 AM, Qian Hong wrote:
> On Thu, Jan 7, 2016 at 1:23 PM, Sebastian Lackner <sebastian@fds-team.de> wrote:
>> Wouldn't it be easier to just swap events[0] <-> events[1], to handle the
>> exit event with higher priority? I do not see any real need for two calls
>> to Wait*() functions.
>
>
> After discussing on irc, we agree that swapping events[0] <->
> events[1] is not enough.
> The original patch fix not only one bug, but two separate problems.
> In the existent implementation, If ntrc is never set to
> STATUS_PENDING, then there is no chance to turn exit_now to true,
> Changhui's patch fix this bug, which is discovered by a real world
> online bank driver.
>
My ears perk up here. Real world online bank driver? Can I see and play with it. I am really looking for real world cases that use HID.
-aric