linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Gupta <dceravigupta@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, linuxppc-dev@ozlabs.org
Subject: DMA transfer within kernel space
Date: Wed, 11 Aug 2010 11:39:26 +0530	[thread overview]
Message-ID: <AANLkTikYwtumQVORC6wCFexmHTf90zcyuC1V08PkjhCQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

Hi,

I am new to linux device driver development and I'm trying to learn the
DMA transfer. Currently I have created a  DMA buffer using
pci_alloc_consistent() function. Since I don't have a real DMA enabled pci
device, so I am thinking of transfer the data in the DMA buffer to some
other buffer within kernel space(let say created through kmalloc) using
DMA.

Is it possible to do DMA transfer within kernel space? If yes, please
provide some sample code for the same.

Thanks in advance
Ravi Gupta

[-- Attachment #2: Type: text/html, Size: 541 bytes --]

                 reply	other threads:[~2010-08-11  6:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTikYwtumQVORC6wCFexmHTf90zcyuC1V08PkjhCQ@mail.gmail.com \
    --to=dceravigupta@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@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).