From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: DMA mapping API for non-system memory pools
Date: Fri, 09 Feb 2007 18:53:29 -0500 [thread overview]
Message-ID: <1171065209.3627.38.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <4479FB80-8703-4BCA-925E-DA25B65EE916@kernel.crashing.org>
On Fri, 2007-02-09 at 17:33 -0600, Kumar Gala wrote:
> ideally all this would be handled via the dma mapping API, the
> question is how to convey to the API to use the IO memory vs the
> system memory? Should we look at adding a new GFP_IOMEM flag or do
> something based on struct device?
>
> Any ideas on direction (or if this is a solved problem elsewhere)
> would be appreciated.
Doesn't the dma_declare_coherent_memory() API work for this case? it
was designed for the ARM SoC (and the voyager weird SCSI card).
James
next prev parent reply other threads:[~2007-02-09 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 23:33 Kumar Gala
2007-02-09 23:53 ` James Bottomley [this message]
2007-02-09 23:54 ` Matthew Jacob
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=1171065209.3627.38.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@hansenpartnership.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®