From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur.tabi@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
Dan Malek <ppc6dev@digitaldans.com>,
Dan Williams <dan.j.williams@intel.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
Becky Bruce <beckyb@kernel.crashing.org>
Subject: Re: [PATCH] fsldma: add support to 36-bit physical address
Date: Wed, 22 Sep 2010 00:41:43 -0500 [thread overview]
Message-ID: <492E9153-2D3E-4DA2-AD04-4F92C94DB3A7@kernel.crashing.org> (raw)
In-Reply-To: <AANLkTinbjb+uQdby999rs1eF1sqPHY2vXJ1mVrznFv=0@mail.gmail.com>
On Sep 21, 2010, at 5:34 PM, Timur Tabi wrote:
> On Tue, Sep 21, 2010 at 5:17 PM, Scott Wood <scottwood@freescale.com> wrote:
>
>> It needs to be the actual device that is performing the DMA -- the
>> platform may need to do things such as IOMMU manipulation where
>> knowing the device matters.
>
> Ok, this all makes sense. So it appears that the patch is valid, at
> least in theory. I would like to see some testing of it, but I
> realize that may be too difficult. There's no easy way to force an
> allocation above 4GB.
I think the patch is pretty safe w/o testing. However I agree we need a better solution to testing 36-bit addressing.
- k
next prev parent reply other threads:[~2010-09-22 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:57 Li Yang
2010-09-21 12:55 ` Kumar Gala
2010-09-21 21:24 ` Timur Tabi
2010-09-21 21:34 ` Scott Wood
2010-09-21 21:43 ` Timur Tabi
2010-09-21 21:49 ` Scott Wood
2010-09-21 22:04 ` Timur Tabi
2010-09-21 22:05 ` Dan Malek
2010-09-21 22:08 ` Timur Tabi
2010-09-21 22:17 ` Scott Wood
2010-09-21 22:34 ` Timur Tabi
2010-09-22 5:41 ` Kumar Gala [this message]
2010-09-23 22:11 ` Dan Williams
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=492E9153-2D3E-4DA2-AD04-4F92C94DB3A7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=beckyb@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ppc6dev@digitaldans.com \
--cc=scottwood@freescale.com \
--cc=timur.tabi@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
all inboxes | Powered by JetHome®