Date: Sat, 19 Jun 2004 23:49:33 +0100
From: Ian Molton <spyro@f2s.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: rmk+lkml@arm.linux.org.uk, david-b@pacbell.net,
       linux-kernel@vger.kernel.org, greg@kroah.com, tony@atomide.com,
       jamey.hicks@hp.com, joshua@joshuawise.com
Subject: Re: DMA API issues
Message-Id: <20040619234933.214b810b.spyro@f2s.com>
In-Reply-To: <1087681604.2121.96.camel@mulgrave>
References: <1087584769.2134.119.camel@mulgrave>
	<20040618195721.0cf43ec2.spyro@f2s.co <40D34078.5060909@pacbell.net>
	<20040618204438.35278560.spyro@f2s.com>
	<1087588627.2134.155.camel@mulgrave
	<40D359BB.3090106@pacbell.net>
	<1087593282.2135.176.camel@mulgrave>
	<40D36EDE.2080803@pacbell.net>
	<1087600052.2135.197.camel@mulgrave>
	<40D4849B.3070001@pacbell.net>
	<20040619214126.C8063@flint.arm.linux.org.uk>
	<1087681604.2121.96.camel@mulgrave>
Organization: The Dragon Roost
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 857
Lines: 19

On 19 Jun 2004 16:46:42 -0500
James Bottomley <James.Bottomley@SteelEye.com> wrote:

> 
> But we still need some sort of fallback where the platform really
> cannot do this.  And that fallback is going to be ioremap and all the
> other paraphenalia.  So, the thing that bothers me is that if we have
> to have the fallback which is identical to what every other driver
> that uses on-chip memory does anyway, is there any point to placing
> this in the DMA API?

Can you describe a system where its impossible to use the DMA API or one
of the modifications proposed here? what sort of hardware does this and
why?
-
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/