From owner-freebsd-usb@FreeBSD.ORG Thu Oct 10 06:45:34 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D5BF3F37 for ; Thu, 10 Oct 2013 06:45:34 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 90B80231A for ; Thu, 10 Oct 2013 06:45:34 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id 0D63D7A13A; Thu, 10 Oct 2013 08:28:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 744298F5E0E; Thu, 10 Oct 2013 08:28:47 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6stM-JV-AkRS; Thu, 10 Oct 2013 08:28:46 +0200 (CEST) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) by mail.lockless.no (Postfix) with ESMTPSA id 2F3C18F2C8D; Thu, 10 Oct 2013 08:28:46 +0200 (CEST) Message-ID: <52564953.8080707@bitfrost.no> Date: Thu, 10 Oct 2013 08:29:39 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130522 Thunderbird/17.0.6 MIME-Version: 1.0 To: Daniel O'Connor Subject: Re: USB config SX lock deadlock References: <9783900F-08A1-41FB-81B8-3C9809B82521@gsoft.com.au> <52553000.2010003@bitfrost.no> <52554855.6030404@bitfrost.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 06:45:34 -0000 On 10/09/13 23:25, Daniel O'Connor wrote: > > On 09/10/2013, at 22:43, Hans Petter Selasky wrote: >> On 10/09/13 12:38, Daniel O'Connor wrote: >>> On 09/10/2013, at 20:59, Hans Petter Selasky wrote: >>> It is actually running r253505, sorry I should have mentioned that before. >>> >>> It isn't a serial device, although the driver is a thin wrapper around the usb_fifo code (which is very useful - thanks :) >> >> Does your application close the file handle when it gets a read/poll error? > > > It might under some circumstances but not directly. > > It has 3 sub interfaces, if there is an error on one the the DAQ program will call abort() which would result in FDs being closed. > > However that sub interface does not use read/poll only ioctl. > Hi, How do these IOCTLs work? Do you wakeup any sleepers at "surprise" detach? --HPS