From: "suresh suresh" <sureshtang@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org, Siva Prasad <sprasad@bivio.net>
Subject: Re: Linuxppc-embedded Digest, Vol 35, Issue 33
Date: Tue, 17 Jul 2007 11:29:04 +0530 [thread overview]
Message-ID: <e5eb93010707162259l2e78c524s32ff260b3d930bdb@mail.gmail.com> (raw)
In-Reply-To: <469B9825.6070507@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Thanks....
MPC8280 has internal memory space which contains Dualport(Dp) RAM. In the
DpRAM we allocate some tables and these has to store pointer of the buffers
which are allocated in external memory. Core will use this pointer to access
the buffers, basically these buffers are used for DMA.
Using IMMR register we can get physical address of the internal memory. Now
can I store the address return by the kmalloc() function? or I should
convert it into physical?
Please help me how to resove this address translation.
Regards,
Suresh
On 7/16/07, Scott Wood <scottwood@freescale.com> wrote:
>
> Siva Prasad wrote:
> > It returns kernel virtual address. If you use this buffer space for DMA,
> > please use appropriate flags. You may use __pa(address) or
> > virt_to_phys() to convert virtual to physical.
>
> No, you may not -- physical and DMA addresses are not always identical.
> Use the DMA mapping API.
>
> -Scott
>
>
[-- Attachment #2: Type: text/html, Size: 1281 bytes --]
next prev parent reply other threads:[~2007-07-17 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1061.1184600645.8639.linuxppc-embedded@ozlabs.org>
2007-07-16 15:58 ` Linuxppc-embedded Digest, Vol 35, Issue 33 Siva Prasad
2007-07-16 16:09 ` Scott Wood
2007-07-17 5:59 ` suresh suresh [this message]
2007-07-17 16:02 ` Scott Wood
2007-07-17 22:41 ` Siva Prasad
2007-07-17 22:51 ` Scott Wood
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=e5eb93010707162259l2e78c524s32ff260b3d930bdb@mail.gmail.com \
--to=sureshtang@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=sprasad@bivio.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;
as well as URLs for NNTP newsgroup(s).