[argyllcms] Re: concurrent timeout patch for libusb is causing regression in pilot-link
- From: Graeme Gill <graeme@xxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 10 Sep 2008 22:14:48 +1000
Frederic Crozat wrote:
for the record, we just discovered a regression caused by your
concurrent timeout patch on libusb (the first version was Logitech G15
mouse/keyboard, the latest version was no longer regressing) :
pilot-link (Palm pda support library) are not longer able to detect
palm is connected over usb (through libusb).
I guess that someone with a pilot-link had better figure it out then. When
they do, I'll be more than happy to regression test against the color
instruments I have. Of course the simplest way of solving the problem
in the short term, would be to revert the changes to your system
library libusb, and to link argyllcms to it's own copy of libusb, just
as I do in my distribution. [Of course it's possible that the bug
is actually in the way the pilot-link library is using libusb,
and that the concurrency fix merely exposes the bug].
Graeme Gill.
- References:
- [argyllcms] concurrent timeout patch for libusb is causing regression in pilot-link
- From: Frederic Crozat
Other related posts:
- » [argyllcms] concurrent timeout patch for libusb is causing regression in pilot-link
- » [argyllcms] Re: concurrent timeout patch for libusb is causing regression in pilot-link
for the record, we just discovered a regression caused by your concurrent timeout patch on libusb (the first version was Logitech G15 mouse/keyboard, the latest version was no longer regressing) : pilot-link (Palm pda support library) are not longer able to detect palm is connected over usb (through libusb).
- [argyllcms] concurrent timeout patch for libusb is causing regression in pilot-link
- From: Frederic Crozat