From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Discussion about iopa()
Date: Fri, 9 Feb 2007 17:22:34 -0600 [thread overview]
Message-ID: <969E3C07-96EE-4AF9-BF57-B10F049684EE@kernel.crashing.org> (raw)
In-Reply-To: <45CCFF4B.7000102@freescale.com>
On Feb 9, 2007, at 5:10 PM, Timur Tabi wrote:
> Kumar Gala wrote:
>
>> It doesn't seem like it's that big of a change. I'd rather the
>> code clearly do different things for MURAM vs system memory for
>> ALL accesses.
>
> Why? MURAM acts like RAM, it just needs to be mapped first.
It does from a coherence point of view, but not from an allocation
mechanism.
We should fix it so the driver just has to do dma_alloc_coherent,
dma_free_coherent, and dma_map_*/dma_unmap_*
- k
next prev parent reply other threads:[~2007-02-09 23:23 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 11:31 [PATCH 1/4] ucc_geth: Change private immrbar_virt_to_phys to generic iopa Li Yang
2007-02-06 14:26 ` Kumar Gala
2007-02-06 14:26 ` Kumar Gala
2007-02-07 9:34 ` Li Yang-r58472
2007-02-07 9:34 ` Li Yang-r58472
2007-02-07 16:36 ` Kumar Gala
2007-02-07 16:36 ` Kumar Gala
2007-02-07 16:43 ` Timur Tabi
2007-02-07 16:43 ` Timur Tabi
2007-02-07 16:49 ` Kumar Gala
2007-02-07 16:49 ` Kumar Gala
2007-02-07 17:03 ` Timur Tabi
2007-02-07 17:03 ` Timur Tabi
2007-02-08 5:52 ` Li Yang-r58472
2007-02-08 5:52 ` Li Yang-r58472
2007-02-08 5:57 ` Kumar Gala
2007-02-08 6:48 ` Li Yang-r58472
2007-02-08 6:48 ` Li Yang-r58472
2007-02-08 6:53 ` Kumar Gala
2007-02-08 6:53 ` Kumar Gala
2007-02-08 7:06 ` Li Yang-r58472
2007-02-08 7:06 ` Li Yang-r58472
2007-02-08 7:16 ` Kumar Gala
2007-02-08 7:16 ` Kumar Gala
2007-02-08 7:36 ` Li Yang-r58472
2007-02-08 7:36 ` Li Yang-r58472
2007-02-08 7:41 ` Kumar Gala
2007-02-08 7:41 ` Kumar Gala
2007-02-08 9:22 ` Discussion about iopa() Li Yang-r58472
2007-02-08 13:41 ` Timur Tabi
2007-02-09 17:08 ` Dan Malek
2007-02-10 2:37 ` Benjamin Herrenschmidt
2007-02-10 18:04 ` Dan Malek
2007-02-10 21:40 ` Benjamin Herrenschmidt
2007-02-10 22:27 ` Dan Malek
2007-02-10 22:42 ` Benjamin Herrenschmidt
2007-02-08 21:26 ` Benjamin Herrenschmidt
2007-02-09 17:13 ` Dan Malek
2007-02-09 22:06 ` Benjamin Herrenschmidt
2007-02-09 22:46 ` Kumar Gala
2007-02-09 22:51 ` Timur Tabi
2007-02-09 23:06 ` Kumar Gala
2007-02-09 23:10 ` Timur Tabi
2007-02-09 23:19 ` Benjamin Herrenschmidt
2007-02-09 23:22 ` Kumar Gala [this message]
2007-02-09 23:33 ` Timur Tabi
2007-02-09 23:43 ` Kumar Gala
2007-02-09 17:06 ` Dan Malek
2007-02-08 13:35 ` [PATCH 1/4] ucc_geth: Change private immrbar_virt_to_phys to generic iopa Timur Tabi
2007-02-08 13:35 ` Timur Tabi
2007-02-09 17:22 ` Dan Malek
2007-02-09 17:26 ` Timur Tabi
2007-02-09 17:26 ` Timur Tabi
2007-02-08 13:27 ` Timur Tabi
2007-02-07 0:19 ` Jeff Garzik
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=969E3C07-96EE-4AF9-BF57-B10F049684EE@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.