From owner-freebsd-current@FreeBSD.ORG Tue Dec 9 14:57:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB6031065672 for ; Tue, 9 Dec 2008 14:57:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8144D8FC19 for ; Tue, 9 Dec 2008 14:57:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mB9EvMZC029901; Tue, 9 Dec 2008 09:57:22 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mB9EvLSD047534 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 09:57:21 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200812091457.mB9EvLSD047534@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 09 Dec 2008 09:57:20 -0500 To: Marcel Moolenaar From: Mike Tancsa In-Reply-To: <7.1.0.9.0.20081208173515.13f62e88@sentex.net> References: <200812081621.mB8GLMxB041498@lava.sentex.ca> <200812081906.mB8J6oha042222@lava.sentex.ca> <200812082049.mB8KnHSN042710@lava.sentex.ca> <84A7F176-5A74-48AC-859A-C0D4C7CBCB48@mac.com> <7.1.0.9.0.20081208173515.13f62e88@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-current@freebsd.org Subject: Re: uart vs sio differences ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 14:57:24 -0000 At 05:39 PM 12/8/2008, Mike Tancsa wrote: >What it appears to be is that as long as data is coming in, even at >1200bps, the ioctl FIONREAD returns zero and an actual read does not >return any data until there is either a pause in the data coming in >or possibly when we do a xmit/write at which point the accumulated >data is available for us to read. > >We dont know if this is due to the hardware fifo or something in the >driver itself. OK, I think we found the issue! http://www.freebsd.org/cgi/query-pr.cgi?pr=121421 Not sure if the semantics are exactly right, but adding hint.uart.0.flags="0x100" hint.uart.1.flags="0x100" hint.uart.2.flags="0x100" hint.uart.3.flags="0x100" to device.hints fixed the issue! The next question-- is there a way to do this with the ucom driver as well ? We are seeing the same issue with it. ---Mike