| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Instead of only returning 0 or 1, this can be used for flowcontrol purposes.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
So cleanup on failure to re-claim after a set_config, and let our user know
that we've lost the device with a new usbredirhost_read_device_lost status.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
See the description of the new usbredirhost_set_device() function in
usbredirhost/usbredirhost.h
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Make this conditional on the same cap as device_reject, rename
the cap to usb_redir_cap_filter. Rename device_reject to filter_reject to
reflect that it is filtering related and that the the cap and packet names
are consistent with each other. Also cleanup some related comments / docs.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Add an usb_redir_device_reject packet to allow notifying the usb-host when
an usb-guest rejects a device because of usb-guest side device filtering.
Also bump the version to 0.3.4 so that apps can check if libusbredirparser /
libusbredirhost knows about usb_redir_device_reject by checking the version
number.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Add usbredirfilter code, to help apps exclude certain devices from
redirection. See the new usbredirfilter.h for details.
This commit also bumps the reported version to 0.3.3, so that apps using
libusbredirparser can check for this version to check the presence of the
new usbredirfilter functions.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
Having separate set_locking_funcs functions causes the locking functions
to be available potentially too late. And it just is not very pretty.
This commit changes the API (in a way which is backward compat with 0.3.1), so
that locking functions can be specified at creation time, just like all the
other callbacks.
This commit also bumps the reported version to 0.3.2, so that apps using
libusbredirhost can check for this version to check the presence of the new
usbredirhost_open_full function.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
Document that libusbredirhost_open closes the past in libusb device handle
on failure, and make sure this is always true.
|
|
|
|
|
|
This:
-fixes a memleak where we would not free the transfer + transfer buffer
for iso / int transfers
-stops libusb from complaining there are still transfers pending on device
close
|
|
When cancelling an active iso stream some iso packets will likely complete
while we are cancelling, but we will see them as uncomplete as long as we've
not asked libusb to check for complete transfers, this is inherently racy and
there is nothing we can do. Thus we will sometimes try to cancel already
completed transfers which will fail.
This is not a problem, but libusb spews ugly error messages to stderr when
this happens. This patch silences these error messages.
|
|
|
