From owner-freebsd-usb@FreeBSD.ORG  Mon Oct  4 10:48:12 2010
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 44BE41065695
	for <freebsd-usb@freebsd.org>; Mon,  4 Oct 2010 10:48:12 +0000 (UTC)
	(envelope-from br@bsdjail.com)
Received: from bsdpad.com (bsdpad.com [81.19.69.224])
	by mx1.freebsd.org (Postfix) with ESMTP id F23778FC12
	for <freebsd-usb@freebsd.org>; Mon,  4 Oct 2010 10:48:11 +0000 (UTC)
Received: from [81.19.69.226] (helo=bsdjail.com)
	by bsdpad.com with esmtp (Exim 4.71 (FreeBSD))
	(envelope-from <br@bsdjail.com>) id 1P2hwP-0000yW-Jr
	for freebsd-usb@freebsd.org; Mon, 04 Oct 2010 14:06:41 +0400
Received: (from br@localhost)
	by bsdjail.com (8.14.4/8.14.4/Submit) id o94A6fUb003751
	for freebsd-usb@freebsd.org; Mon, 4 Oct 2010 14:06:41 +0400 (MSD)
	(envelope-from br)
Date: Mon, 4 Oct 2010 14:06:41 +0400
From: Ruslan Bukin <br@bsdpad.com>
To: freebsd-usb@freebsd.org
Message-ID: <20101004100641.GA3403@bsdjail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Broken-Reverse-DNS: no host name for IP address 81.19.69.226
Subject: /dev/ttyU0 - block at open
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: Mon, 04 Oct 2010 10:48:12 -0000

Hi!

I am using u3g driver for Gobi 2000 QDL device.
The open ("/dev/ttyU0", O_RDWR) does not return anything,
But it returns immediately with only O_NONBLOCK or O_NDELAY flags.

is it normal behavior or not?

The device is answering for commands normally in non-block state,
but only returns error when I try to write firmware to it.

I think may be the problem is in block/non-block modes.

Thanks

-Ruslan