USBB2K-API - Patches: patch #5967, A better patch to issue new events...
You are not allowed to post comments on this tracker with your current authentication level.
patch #5967: A better patch to issue new events only on socket
Submitter: | None | ||
Submitted: | Thu 24 May 2007 08:50:15 PM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Email: | -email is unavailable- |
Open/Closed: | Open |
Attached Files
file #12850: ADNAMS_usbb2k-api.patch added by None (5KiB - text/x-patch)
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2007-05-24 | None | Attached File | - | Added ADNAMS_usbb2k-api.patch, #12850 |
Powered by Savane 3.13-cf05.
Corresponding source code
This is a replacement for the previously submitted patch. It does essentially the same thing, but in this one we're a little more careful about error handling, and some of the syslog chatter has been commented out. This patch was produced for use with kb2kskype, using a companion patch for those sources, but it is not specific to that package.
Note that with this (and the unpatched) driver, the telbox does consistently issue two random keypress events after switching from PSTN to USB mode. Switching from USB to PSTN mode, the driver will report two random keypresses sometimes. I am just guessing, but I think these might not be keypresses, but attempts by the telbox to exercise the tail end of a mode-switching protocol (to inform the driver about its state. In any case, developers should not that client software needs to be able to cope smoothly with this behaviour.