linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Kleinosowski <kevinko@arlut.utexas.edu>
To: linuxppc-embedded@ozlabs.org
Subject: 440gx dma transfer with no data change at dest
Date: Tue, 7 Mar 2006 15:16:08 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0603071505110.21479@mohave.arlut.utexas.edu> (raw)


I am running a simple test with a software initiated DMA transfer from one 
bigphysarea allocated buffer to another bigphysarea allocated buffer. 
The destination buffer shows no data changes once the transfer is done.

However, I perform the same simple test using __get_dma_pages() rather 
then the bigphysarea_alloc_pages() and the destination does get the 
data transfer.

Is there a reason this should fail for bigphysarea?  I understand the low 
memory addresses needed for the DMA controller on some platforms, but I 
didnt think that limitation existed on the PPC.  Besides that, the 
bigphysarea returns low memory address anyway.  Anyone have an idea why? 
An old archive email had someone with a similar problem, but there were no 
follow-ups to the message.

I have linux 2.4.27-pre3 patched, ppc-linux-gcc (GCC) 3.3.3 (DENX ELDK 
3.1.1 3.3.3-9), U-Boot 1.1.2, and GMS 440gx board.

thanks,
Kevin

             reply	other threads:[~2006-03-07 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 21:16 Kevin Kleinosowski [this message]
2006-03-10 22:07 ` 440gx dma transfer with no data change at dest Kevin Kleinosowski
  -- strict thread matches above, loose matches on Subject: below --
2006-05-26 20:58 John Lange

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=Pine.LNX.4.64.0603071505110.21479@mohave.arlut.utexas.edu \
    --to=kevinko@arlut.utexas.edu \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).