Subject: Re: [RFC][PATCH] TTY flip buffer SMP changes
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Paul Fulghum <paulkf@microgate.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <1097286154.5592.9.camel@gaston>
References: <1097179099.1519.17.camel@deimos.microgate.com>
	 <1097177830.31768.129.camel@localhost.localdomain>
	 <20041008062650.GC2745@thunk.org>
	 <1097242506.2008.30.camel@deimos.microgate.com>
	 <1097239894.2290.13.camel@localhost.localdomain>
	 <20041008150055.GA13870@thunk.org>  <1097286154.5592.9.camel@gaston>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1097368333.6128.2.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Sun, 10 Oct 2004 01:32:15 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 909
Lines: 18

On Sad, 2004-10-09 at 02:42, Benjamin Herrenschmidt wrote:
> That reminds me... a while ago, I toyed with the idea of having DMA
> support in pmac_zilog. The case where it would work well is typically
> for things that have a known sized frame. If that information was
> provided down to the driver, I could setup the DMA descriptor for
> that frame size & have it interrupt me when the frame is complete,
> along with a timeout set to the estimated time for receiving such
> a frame + X% (I was thinking +20%)

I thought the 85C30 only supported DMA for sync modes ? We have sync
8530 DMA code for ISA bus already, which I never got around to adding
async too 8)

-
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/