Re: [MOD] STR #4128: libusb-based USB backend: Further fixes

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

FYI regarding "USB device reset after finishing each job":

On all-in-one USB devices a USB device reset (i.e. a reset of
the whole USB device) may have bad side-effects, see
https://bugzilla.novell.com/show_bug.cgi?id=751712#c10

In this case an all-in-one USB device reset because
of an issue of the mass-storage unit caused an abort
of the print job which printed at the same time.

In other words: A reset of a whole USB all-in-one device
may cause abort of whatever runs at the same time on
whatever other units of the all-in-one USB device.

According to
https://bugzilla.novell.com/show_bug.cgi?id=751712#c12
the root cause of such bad side-effects seems to be
an insufficiency in the USB all-in-one device but
as far as I see this STR is mainly about how to deal
gracefully with insufficiencies in USB devices.

I don't know if particular hardware like the Prolific
USB->Parallel adaptor justifies to do a USB device reset
in any case after finishing each job.

Till,
is the "quirks"-behaviour of the libusb-based USB backend
configurable by the admin (e.g. via DeviceURI options)
or is it hardcoded?

Link: http://www.cups.org/str.php?L4128
Version: 1.6-current