Date: Tue, 22 Sep 2009 17:35:56 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: "Pierre-Luc Drouin" <pldrouin@pldrouin.net> Cc: ed@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/138659: uftdi driver broken in RELENG_8/CURRENT Message-ID: <200909221735.57680.hselasky@c2i.net> In-Reply-To: <4AB8EB78.2020809@pldrouin.net> References: <4AB6DA79.7050209@pldrouin.net> <200909221638.47642.hselasky@c2i.net> <4AB8EB78.2020809@pldrouin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909221735.57680.hselasky>