From: Matt Porter <mporter@kernel.crashing.org>
To: Sachin P <sachinpc@gmail.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: consistent_alloc() on PPC
Date: Wed, 19 Jan 2005 07:04:46 -0700 [thread overview]
Message-ID: <20050119070445.A448@home.com> (raw)
In-Reply-To: <66164fbc0501190353485dc8e4@mail.gmail.com>; from sachinpc@gmail.com on Wed, Jan 19, 2005 at 05:23:17PM +0530
On Wed, Jan 19, 2005 at 05:23:17PM +0530, Sachin P wrote:
> Hi ,
> I am facing some problems porting my drivers to the PPC platform . Am
> currently using consistent_alloc() and consistent_free() to
> allocate/free (non-cached) DMA ble memory.
> Is there any function/patch/macro, equivalent to
> phy_to_virt()/virt_to_phy() for memory returned by consistent_alloc()?
iopa()
-Matt
next prev parent reply other threads:[~2005-01-19 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 11:53 consistent_alloc() on PPC Sachin P
2005-01-19 14:04 ` Matt Porter [this message]
2005-01-19 14:10 ` Christoph Hellwig
2005-01-19 14:56 ` Matt Porter
2005-01-20 16:30 ` Sachin P
2005-01-20 18:16 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 11:53 Sachin P
2005-01-19 15:14 ` Jörn Engel
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=20050119070445.A448@home.com \
--to=mporter@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=sachinpc@gmail.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).