usb/138659: uftdi driver broken in RELENG_8/CURRENT

[Hans Petter Selasky]

On Tuesday 22 September 2009 17:21:28 Pierre-Luc Drouin wrote:

> >> Thanks!
> >
> > It indicates that your device is not sending any data.
> >
> > --HPS
>
> So does it mean that the write statement (a status request) is not
> transmitted to the device either?

No, the "xxx_get()" message means that the data you write is sent and 
transmitted.

BTW: I have a FTDI adapter here, and it works fine with loopback when the 
baudrate is set correctly.

> Because this write statement should be
> followed by data sent from the device and it effectively does on Linux.
> And about SIGIO, shouldn't this signal be generated only when there is
> data available to read? Why is it generated in asynchronous mode and
> then the read statement returns EINTR?

Ed has to answer these questions. This stuff is not handled in the USB stack 
for FTDI devices.

--HPS