From: coolsandyforyou@gmail.com (sandeep kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How DMA transfers > 2MB are being performed?
Date: Wed, 1 Jun 2011 10:40:55 +0530 [thread overview]
Message-ID: <BANLkTimEyoDGdLT+_fOOiWSqdSZ1BhYOOQ@mail.gmail.com> (raw)
Hi all
A very limited (1-2MB) address space is mapped to dma_alloc() in ARM
architecture..what if a DMA transfer of >2MB is needed at a time? As DMA
transfer starts asynchronously..CPU relinquishes data buses..so CPU cant
control. So the excess data which is >2MB will be overflown or lost..So how
this large data transfers are being managed?
--
With regards,
Sandeep Kumar Anantapalli,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110601/9ef6420c/attachment.html
next reply other threads:[~2011-06-01 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 5:10 sandeep kumar [this message]
2011-06-01 6:00 ` How DMA transfers > 2MB are being performed? Dave Hylands
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=BANLkTimEyoDGdLT+_fOOiWSqdSZ1BhYOOQ@mail.gmail.com \
--to=coolsandyforyou@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).