From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Mark Hounschell <markh@compro.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: problems doing direct dma from a pci device to pci-e device
Date: Mon, 14 Sep 2009 04:03:17 -0400 [thread overview]
Message-ID: <4AADF8C5.2000205@cfl.rr.com> (raw)
In-Reply-To: <20090914053610.GA5970@lackof.org>
Grant Grundler wrote:
> On Fri, Sep 11, 2009 at 04:04:00PM -0400, Mark Hounschell wrote:
>> A quick readup on the IOMMU makes me think that if it does use one, that
>> could certainly cause my problem. I'm using bus addresses plugged into
>> page tables that live in the gpiohsd card obtained from virt2bus.
>
> If you haven't yet, take a look at Documentation/DMA-API.txt and
> DMA-mapping.txt . virt2bus has been deprecated for DMA since 2.4 releases.
>
> grant
> --
> 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/
>
It still gives me a bus address just fine. Actually when the gpiohsd is dmaing
into another card I don't use it. I misspoke. The VMIC cards library API gives
me its memory's bus address.
Mark
next prev parent reply other threads:[~2009-09-14 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 14:13 problems doing direct dma from a pci device to pci-e device Mark Hounschell
2009-09-11 14:41 ` Richard B. Johnson
2009-09-11 14:50 ` Mark Hounschell
2009-09-11 14:47 ` Alan Cox
2009-09-11 15:25 ` Mark Hounschell
2009-09-11 15:46 ` Richard B. Johnson
2009-09-11 19:42 ` Mark Hounschell
2009-09-11 20:04 ` Mark Hounschell
2009-09-14 5:36 ` Grant Grundler
2009-09-14 8:03 ` Mark Hounschell [this message]
2009-09-15 11:23 ` Mark Hounschell
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=4AADF8C5.2000205@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=markh@compro.net \
/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