From: Scott Wood <scottwood@freescale.com>
To: rmcguire@videopresence.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: virt_to_phys() in drivers w/dma - MPC8xxx
Date: Mon, 25 Aug 2008 10:33:30 -0500 [thread overview]
Message-ID: <48B2D0CA.10602@freescale.com> (raw)
In-Reply-To: <6FC450394F2147FDB7EC1D1EB168EB8B@absolutdaddy>
Russell McGuire wrote:
> So shouldn't we be using like dma_alloc_coherent, and then tracking the dma
> address separately as a variable, and use it when necessary instead of
> calling virt_to_phys()?
Yes. On 8xxx (but not 8xx, and not with 36-bit memory), there'll be no
practical difference, but the DMA mapping API *should* be used.
-Scott
prev parent reply other threads:[~2008-08-25 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1217383202.19379.linuxppc-embedded@ozlabs.org>
2008-08-20 23:49 ` ELDK Fedora Core 9 Russell McGuire
2008-08-21 10:10 ` Wolfgang Denk
2008-08-22 23:14 ` virt_to_phys() in drivers w/dma - MPC8xxx Russell McGuire
2008-08-25 15:33 ` Scott Wood [this message]
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=48B2D0CA.10602@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rmcguire@videopresence.com \
/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;
as well as URLs for NNTP newsgroup(s).