From owner-freebsd-usb@FreeBSD.ORG Tue Sep 22 16:32:21 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 744F7106566C; Tue, 22 Sep 2009 16:32:21 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.tele2.se [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id D23068FC0A; Tue, 22 Sep 2009 16:32:20 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=6U-Pe18MTAwA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=iUV8EKD_c1rD5WRaTq4A:9 a=Qa9utn3zGSLP6tp8Y6cA:7 a=zT_VQ58tYyIJRjXs3ouBTdTqd_0A:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 567291388; Tue, 22 Sep 2009 18:32:18 +0200 From: Hans Petter Selasky To: "Pierre-Luc Drouin" Date: Tue, 22 Sep 2009 18:32:55 +0200 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4AB6DA79.7050209@pldrouin.net> <200909221735.57680.hselasky@c2i.net> <4AB8F817.1040703@pldrouin.net> In-Reply-To: <4AB8F817.1040703@pldrouin.net> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909221832.56540.hselasky@c2i.net> Cc: ed@freebsd.org, freebsd-usb@freebsd.org Subject: Re: usb/138659: uftdi driver broken in RELENG_8/CURRENT X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2009 16:32:21 -0000 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