Date: Tue, 22 Sep 2009 12:40:40 -0400 From: Pierre-Luc Drouin <pldrouin@pldrouin.net> To: Hans Petter Selasky <hselasky@c2i.net> Cc: ed@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/138659: uftdi driver broken in RELENG_8/CURRENT Message-ID: <4AB8FE08.7040007@pldrouin.net> In-Reply-To: <200909221832.56540.hselasky@c2i.net> References: <4AB6DA79.7050209@pldrouin.net> <200909221735.57680.hselasky@c2i.net> <4AB8F817.1040703@pldrouin.net> <200909221832.56540.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hans Petter Selasky wrote: > On Tuesday 22 September 2009 18:15:19 Pierre-Luc Drouin wrote: > >> Hans Petter Selasky wrote: >> >>> 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 >>> >> In the manual page for the uftdi driver, the chip I am using (FT232BL) >> is not listed. According to the FTDI website, it is based on FT8U232AM, >> but it has extra functionalities. Have you had the chance to test an >> device that uses either a FT232BM, FT232BL or FT232BQ chip? I just >> tested the device on FreeBSD 7.2 and it does not work either... >> > > No, I haven't. > > --HPS > > Are there additional tests I can do in synchronous mode to try pinning down the problem? Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AB8FE08.7040007>