From mboxrd@z Thu Jan 1 00:00:00 1970 From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen) Subject: Re: Very strange data loss with jsm driver Date: Fri, 29 Jul 2011 14:13:37 -0400 Message-ID: <20110729181337.GM8562@caffeine.csclub.uwaterloo.ca> References: <20110729160416.GK8562@caffeine.csclub.uwaterloo.ca> <20110729172736.4b199d31@lxorguk.ukuu.org.uk> <20110729165342.GB8566@caffeine.csclub.uwaterloo.ca> <20110729180650.GL8562@caffeine.csclub.uwaterloo.ca> <20110729191442.35d09111@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caffeine.csclub.uwaterloo.ca ([129.97.134.17]:44929 "EHLO caffeine.csclub.uwaterloo.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751282Ab1G2SNi (ORCPT ); Fri, 29 Jul 2011 14:13:38 -0400 Content-Disposition: inline In-Reply-To: <20110729191442.35d09111@lxorguk.ukuu.org.uk> Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: Alan Cox Cc: Lennart Sorensen , linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, Breno Leitao On Fri, Jul 29, 2011 at 07:14:42PM +0100, Alan Cox wrote: > > I noticed fifosize in the uart_port info is set to 16, even though the > > fifo size is actually 64 bytes as all actual driver bits know. What is > > fifosize actually used for? > > Only within the driver. The generic code merely knows how it as a > configuration property but doesn't use it. Well the driver certainly never uses that value. I guess setserial can poke at it, but it won't do anything with it. I wonder how I should go about trying to figure out why the driver acts so strangely with this particular input pattern. It seems it can't be the tty layer, since other serial drivers seem to work fine. It has to be the jsm. -- Len Sorensen