Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: Re: Strange problem with tty layer
Date: Wed, 24 Jan 2007 15:19:53 -0600
Message-ID: <335DD0B75189FB428E5C32680089FB9F012DCACD@mtk-sms-mail01.digi.com>
Thread-Topic: Re: Strange problem with tty layer
Thread-Index: Acc//WS/Jid8cj1hQEGs0os0Dc3djg==
From: "Kilau, Scott" <Scott_Kilau@digi.com>
To: <lsorense@csclub.uwaterloo.ca>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1360
Lines: 41

Hi Len,

> I am seeing a very strange problem which seems to be in the tty layer.
> 
> I am using an exar 17D154 based PCI card (like the digi neo style
card)
> using the jsm driver.  Kernel version 2.6.16.25.

There are a couple interesting things I would do here.

1) The tty "flip" buffer stuff was changed in 2.6.16+.

Maybe you could try going downwards to 2.6.15 or below and see if the
problem
still exists.

Then try going up to 2.6.19, I believe there were some bugs fixed
in 2.6.17/18/19, not sure how many of those made it backported into
2.6.16.25.

2) Try using Digi's "Out-Of-Kernel-Source-Tree"/GPL version of the
driver.
You can grab the latest and greatest beta version of it from here:
ftp://ftp1.digi.com/support/beta/linux/dgnc/
Its in source rpm format, let me know if you need it in a tarball format
instead.

You obviously will have to add in your specific PCI id into the driver,
but that should be a problem.

3) I seem to recall that someone mentioned that the Exar 17D154 PCI
chips were
easily "pushed" into the 8250 driver.
It might be interesting to try that route as well.

Scott Kilau
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/