On Tuesday, July 27, 2010 05:58:21 pm DJ Delorie wrote:
> I do the same thing with my FT232RL's. The issue is, when you grab
> the USB device with the FTDI library (or the D2xx library), you grab
> the whole device - including the serial port. At that point, you need
> to use the libftdi API to see the serial port, not Linux's built-in
> tty driver.
> Basically, you can't have two drivers talking to the same usb device
> at the same time.
Aha... Ok. I tried unloading and reloading the module afterward and I still do
not seem to get the serial device back. I need to pull the cable or issue a
USBDEVFS_RESET IOCTL call to the the hub that the FT232R is connected to
(issuing the IOCTL to the FT232R isn't enough).
I also read that the internal EEPROM must match what I tell ftdi_set_bitmode()
call, which is a drag.
Offhand, how do you control CBUS4? There aren't enough bits in the bitmode call
to control it.
-A.
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
