Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2016-01-28 | device: Plug small memory leak | 1 | -0/+1 | ||
2014-11-11 | Get USB speed for device and use it for device attached client message | 1 | -0/+2 | ||
2014-10-06 | Update and slightly cleanup copyright headers | 1 | -19/+18 | ||
2014-09-19 | Flush input buffer for a client connection when calling connection_teardown(). | 1 | -0/+16 | ||
Signed-off-by: Martin Szulecki <m.szulecki@libimobiledevice.org> | |||||
2014-05-27 | Use protocol version 2 by default | 1 | -1/+1 | ||
2014-05-27 | device: Add protocol version 2 support | 1 | -12/+83 | ||
2014-05-07 | Fix connection abort if device buffer is full | 1 | -3/+4 | ||
When trying to upload a IPSW filesystem to an iPad, the process would randomly stop somewhere at 3% or 10%. It is possible that the receive buffer of the iPad is full. To prevent erroring out because size == conn->sendable == 0, skip reading from the client. There is a similar case where the clients is ready to accept data, but the device has no data to send. Apply a similar fix there. Hopefully the device is fast enough to reply in the next main loop iteration, otherwise the CPU usage of usbmux will spike because the client socket is ready while there is no data to process... | |||||
2014-03-24 | device/utils: move mstime64() into utils since it is generally useful | 1 | -10/+0 | ||
2014-03-24 | device: fix potential integer overflow in mstime64() on 32 bit systems | 1 | -1/+4 | ||
2014-03-24 | device: more aggresively send ACKs when receiving TCP data | 1 | -49/+66 | ||
Before this it seemed that we only ever sent ACK when timing out... Looks like a perf double when reading. | |||||
2014-03-24 | client: add a bunch of comments and function docs | 1 | -1/+55 | ||
2014-03-13 | device: suppress 'error reading from client (0)' which is not actually an error | 1 | -1/+3 | ||
2014-01-09 | device: reduce locking time inside device_get_list() and device_get_count() | 1 | -5/+14 | ||
2014-01-09 | removed trailing \n from usbmuxd_log() messages | 1 | -2/+2 | ||
2014-01-09 | device: suppress "No connection for device" if TH_RST is set | 1 | -1/+1 | ||
2014-01-09 | device/client: make device_get_list() allocate the result buffer itself | 1 | -1/+6 | ||
Using device_get_count() and device_get_list() separately can return different device counts in case there are devices added to the list inbetween these two function calls. To prevent this, device_get_list() will allocate the buffer by itself. | |||||
2014-01-09 | device: make device_list access thread safe | 1 | -0/+38 | ||
2013-12-27 | preflight: replace idevice_event_* with thread safe implementation | 1 | -1/+16 | ||
idevice_event_subscribe() calls usbmuxd_subscribe() which will start a thread waiting for device add/remove events. But this implementation is not able to handle more than one "subscription". However the preflight worker will start a thread for _each_ device resulting in a really messed up situation if more than one device is attached at the same time. This fix will use usbmuxd's internal device_remove function calling a preflight callback to make this implementation thread safe. | |||||
2013-09-30 | device: suppress two compiler warnings with appropriate casts | 1 | -3/+3 | ||
2013-09-19 | make sure usbmuxd -x does not terminate when unpaired devices are still present | 1 | -4/+4 | ||
2013-09-19 | added preflight worker implementation to handle initial device pairing | 1 | -3/+16 | ||
2013-09-17 | silence several compiler warnings | 1 | -1/+1 | ||
2013-09-17 | remove libusbmuxd sources and adapt source tree to use autotools | 1 | -0/+781 | ||
libusbmuxd has been split off and is now managed in a separate repository. By the time of this commit, the repository is: git clone http://git.sukimashita.com/libusbmuxd.git |