Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
usbmux.c: In function ‘usbmux_free_device’:
usbmux.c:412: warning: ‘bytes’ may be used uninitialized in this
function
main.c: In function ‘usbmuxd_client_init_thread’:
main.c:197: warning: dereferencing pointer ‘s_req.55’ does break
strict-aliasing rules
main.c:613: note: initialized from here
main.c:944: warning: ‘j’ may be used uninitialized in this function
Signed-off-by: Nikias Bassen <nikias@gmx.li>
|
|
To do this properly, we just have to send an additional zero length usb
packet when we encounter a packet of size wMaxPacketSize or one of its
multiplicants.
|
|
problem'"
This reverts commit 3d517f6879b0c476a2e1ac9a55bb7d436977e3b6.
|
|
This reverts commit 6fbd2a72122d6bcd70edbf599baa7465e3e9acb6.
|
|
This reverts commit 843db538ed4b75d0d5943f0df5ba7ab1ce4e65f9.
|
|
|
|
Use --disable-hacks to NOT enable hacks like the N*128/N*512 hack when
running configure. Hacks are enabled by default.
|
|
For some strange reason packets that are N*128 bytes long via USB 1.1,
or N*512 bytes long via USB 2.0, the device will not send an answer and
any following packet will cause a connection reset.
See this as a workaround until the usb issue has been resolved.
|
|
|
|
does not complain with messages like handleMuxTCPInput th.th_flags = 0x1, not TH_ACK(0x10)
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Nikias Bassen <nikias@gmx.li>
|