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

…ll present

This allows any client to react and handle pairing errors which includes
password protected devices and alike.

…_id()

This changes allows to replug a device to trigger a new trust dialog if the
user did deny the pairing before.

To prevent the trust dialog from appearing on iOS7 devices we need to make
sure that no PTP access is happening before usbmuxd starts. So we start as
early as possible so the device will be in trusted host state.

With the introduction of iOS 7, devices should start of in the "deactivated"
USB configuration "0" by default to not trigger a trust dialog.
Once the devices are identified, usbmuxd will set the correct USB configuration
itself and immediately run the preflight worker code to ensure a trust
relationship with the host is established. This change fixes the trust dialog
from appearing during hotplug of paired devices. The last remaining issue is
that current kernel code still sets the USB configuration to "1" by default
before the udev rules and thus causes multiple connection beeps.

… unplug

The usbmuxd implementation on Win/OS X does allow enumerating and accessing the
device during the "trust dialog" pairing process. We now also exit the waiting
loop during unplugging of a device while waiting for the trust dialog to be
dismissed.

…cess

…ig dir

…etePairRecord commonds

When a large number of devices are used, the number of open file descriptors
can reach the default system limit. Upon startup we now raise it to
a much higher value to give more 'space'.

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.

… fixed amount

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.

…ount()

…d of larger

…y an error

Before this it seemed that we only ever sent ACK when
timing out... Looks like a perf double when reading.

By maintaining 3 parallel usb trasfers when reading we get 2-3x more
throughput when reading. Without this the usb port is mostly just idling.
I get 23mb/s on my system compared to a clean Apple stack that gives me
17mb/s.

3 was chosen because it is simple to hard code, gives very good performance,
and have very little impact on out resource consumption.

…ug reports