From owner-freebsd-usb@FreeBSD.ORG  Tue Sep 22 16:40:40 2009
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
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 B4FE21065676;
	Tue, 22 Sep 2009 16:40:40 +0000 (UTC)
	(envelope-from pldrouin@pldrouin.net)
Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227])
	by mx1.freebsd.org (Postfix) with ESMTP id 8F2218FC0A;
	Tue, 22 Sep 2009 16:40:40 +0000 (UTC)
Received: from mdaemon.pldrouin.net (pldrouinlap2-pc.physics.carleton.ca
	[134.117.23.34])
	by smtp.cyberfingers.net (Postfix) with ESMTP id 199C5AB6C1D;
	Tue, 22 Sep 2009 12:37:50 -0400 (EDT)
Message-ID: <4AB8FE08.7040007@pldrouin.net>
Date: Tue, 22 Sep 2009 12:40:40 -0400
From: Pierre-Luc Drouin <pldrouin@pldrouin.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090824)
MIME-Version: 1.0
To: Hans Petter Selasky <hselasky@c2i.net>
References: <4AB6DA79.7050209@pldrouin.net>
	<200909221735.57680.hselasky@c2i.net>
	<4AB8F817.1040703@pldrouin.net>
	<200909221832.56540.hselasky@c2i.net>
In-Reply-To: <200909221832.56540.hselasky@c2i.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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 <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 16:40:40 -0000

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!