Nuno wrote:
>> I'm more of a software guy than an hardware guy. This is a FTDI
>> USB-Key [1], which doesn't seem to be possible to open without
>>breaking the plastic (and I'm a zero with a solder iron ;-).
Eh, I looked at the FT232R datasheet just now (instead of the FTDI chip I've
been using), and my idea wouldn't work anyway...it's internal.
>> Maybe I could hack the USB linux driver to force the values read by
>> the kernel (it's not the first time I make a dirty hack on the
>> kernel), but don't even know if the problem is on the kernel or on the
>> device side.
There are people experienced with the kernel over on the libusb-devel list who
could probably help (though somewhat hostile to FTDI). I have no idea if that
would break your other USB devices, though. If you have any luck with this,
it'd be nice if you posted a patch; I'm sure this is not the first time
someone's had a EEPROM problem like this. I generally avoid it by using MPROG
once and *then* loading libftdi/libusb-win32, but that's a hassle.
Michael
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
