>>>>> "Xiaofan" == Xiaofan Chen <xiaofanc@xxxxxxxxx> writes:
Xiaofan> On Tue, May 18, 2010 at 7:40 PM, Thomas Jarosch
Xiaofan> <thomas.jarosch@xxxxxxxxxxxxx> wrote:
>> On Tuesday, 18. May 2010 13:32:39 Uwe Bonnes wrote:
>>> Sorry, next time I will compiled before sending the patch...
>>>
>>> The variable "ret" in the #ifdef'ed code was missing. Appended code
>>> now defines this variable.
>>> -
>> Hmm. I guess we should also ignore the "LIBUSB_ERROR_NOT_SUPPORTED"
>> error code to make this work. Otherwise ftdi_usb_open_dev() will
>> abort...
How much and when have libftdi and libftdi-1.0 diverged?
libftdi stores the result of usb_detach_kernel_driver_np and checks and
reports EPERM with usb_set_configuration() and usb_claim_interface(). The
messages seem quite hintfull for plain users.
Was this introduces after libusb-1.0 was split off? Or was is removed for
any reason?
Should I port the libusb behaviour to 1.0?
--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
