From: James Bottomley <James.Bottomley@steeleye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-arch@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, linux-scsi@vger.kernel.org, jejb@steeleye.com,
Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [PATCH 2/2] Remove dma_coherent_mem interface
Date: Tue, 30 Oct 2007 15:26:31 -0500 [thread overview]
Message-ID: <1193775991.3321.108.camel@localhost.localdomain> (raw)
In-Reply-To: <1193773405-15799-2-git-send-email-matthew@wil.cx>
On Tue, 2007-10-30 at 15:43 -0400, Matthew Wilcox wrote:
> This interface only had one user (and two implementations).
> It complicates other work, so remove it.
Its design was basically to facilitate the use of bus remote memory.
There's a long thread somewhere discussing this with the ARM people.
They had some type of SoC implementation that needed to allocate local
memory for device descriptors. The Q720 is pretty much the same way, so
I used it to build the implementation when I created it for the ARM
people. This is the original thread:
http://marc.info/?t=108757862100001
They said they were implementing this system, so I've no idea what
happened. However, what are the problems the API is causing? it seems
useful, so there should be a preference in its favour of existence
unless it's causing a problem.
James
next prev parent reply other threads:[~2007-10-30 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 19:43 [PATCH 1/2] Wean NCR_Q720 off the dma_declare_coherent_memory interface Matthew Wilcox
2007-10-30 19:43 ` [PATCH 2/2] Remove dma_coherent_mem interface Matthew Wilcox
2007-10-30 20:26 ` James Bottomley [this message]
2007-10-30 20:35 ` Matthew Wilcox
2007-10-31 5:49 ` Paul Mundt
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=1193775991.3321.108.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=hpa@zytor.com \
--cc=jejb@steeleye.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=willy@linux.intel.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).