Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Matthew Wilcox <willy@debian.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>,
	parisc-linux@parisc-linux.org,
	linux-apus-devel@lists.sourceforge.net
Subject: Re: [parisc-linux] Re: NCR53c720
Date: 29 Sep 2003 16:00:10 -0500	[thread overview]
Message-ID: <1064869488.1782.240.camel@mulgrave> (raw)
In-Reply-To: <20030929205548.GA13226@dsl2.external.hp.com>

On Mon, 2003-09-29 at 15:55, Grant Grundler wrote:
> On Mon, Sep 29, 2003 at 05:27:49PM +0100, Matthew Wilcox wrote:
> > > Um, which one is the current right dma device API?
> > 
> > The one in Documentation/DMA-API.txt.
> 
> Matthew, which version of the source tree?
> 2.4.22 and 2.6.x versions of this file are not identical.
> 
> grundler@gsyprf3:/usr/src$ diff linux-2.?/Documentation/DMA-mapping.txt | wc -l
>    117
> grundler@gsyprf3:/usr/src$ wc -l linux-2.?/Documentation/DMA-mapping.txt
>     798 linux-2.4/Documentation/DMA-mapping.txt
>     828 linux-2.5/Documentation/DMA-mapping.txt
>    1626 total

DMA-mapping.txt is only the pci_ DMA API.  The ncr53c8xx doesn't use
that any more.  It only uses the generic DMA API, which is documented in
DMA-API.txt like willy said, and is only in 2.6 (not 2.4).

James

  reply	other threads:[~2003-09-29 21:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.21.0309291116250.7432-100000@vervain.sonytel.be>
     [not found] ` <Pine.LNX.4.44.0309291434260.17812-100000@serv>
2003-09-29 13:33   ` [parisc-linux] Re: NCR53c720 Matthew Wilcox
2003-09-29 13:45     ` Geert Uytterhoeven
2003-09-29 16:24     ` Roman Zippel
2003-09-29 16:27       ` Matthew Wilcox
2003-09-29 20:55         ` Grant Grundler
2003-09-29 21:00           ` James Bottomley [this message]
2003-09-30 17:23             ` Grant Grundler
2003-09-29 21:25     ` Rene Brothuhn
2003-09-30  2:21       ` Matthew Wilcox
2003-09-30  8:21         ` Geert Uytterhoeven
2003-09-30 13:47           ` James Bottomley
2003-09-30 13:59             ` Matthew Wilcox
2003-09-30 15:32               ` James Bottomley
2003-09-30 19:03                 ` Grant Grundler
2003-09-30 13:59         ` Rene Brothuhn
2003-09-30 14:32           ` Matthew Wilcox
2003-10-07 20:22             ` Rene Brothuhn
2003-09-30 14:55           ` Roman Zippel
2003-10-07 20:24             ` Rene Brothuhn
2004-05-04  7:22 Joel Soete

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1064869488.1782.240.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=geert@linux-m68k.org \
    --cc=grundler@parisc-linux.org \
    --cc=linux-apus-devel@lists.sourceforge.net \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=willy@debian.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox