From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "dibacco@libero.it" <dibacco@libero.it>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: __pa giving strange phys address on PPC
Date: Thu, 08 Jan 2009 11:25:08 +1100 [thread overview]
Message-ID: <1231374308.2142.30.camel@pasglop> (raw)
In-Reply-To: <KD4DIL$CAE78B389ABC17D576E1A2B47EE54AEE@libero.it>
On Wed, 2009-01-07 at 22:11 +0100, dibacco@libero.it wrote:
> I used __pa on the result of an uncached_mem_alloc.
No idea what uncached_mem_alloc() is but if that uses the consistent
memory stuff it won't work with __pa.
> Furthermore __pa should work on the return of a kmalloc?
Yes. But don't use that, just use the dma allocation/mapping functions
instead, they return to you both the pa and the dma_addr_t. This is
better for -many- reasons.
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-08 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 21:11 __pa giving strange phys address on PPC dibacco
2009-01-08 0:25 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 20:59 dibacco
2009-01-07 22:27 ` Benjamin Herrenschmidt
2009-01-08 21:03 ` Josh Boyer
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=1231374308.2142.30.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dibacco@libero.it \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).