From: Dan Malek <dan@embeddededge.com>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC85xx DMA support for Kernel 2.6?
Date: Fri, 1 Jul 2005 10:02:54 -0400 [thread overview]
Message-ID: <d946affc11510f7116710026d2a8d1f3@embeddededge.com> (raw)
In-Reply-To: <42C4F50D.3050405@anagramm.de>
On Jul 1, 2005, at 3:47 AM, Clemens Koller wrote:
> .... And currently, when I access (memcopy) the SRAM on my
> Local Bus via UPM I cannot get it to generate bursts yet, so I hope the
> DMA will speed up those things, too.
If the CPU won't do it, the DMA won't either. You better get that
UPM working first :-)
-- Dan
next prev parent reply other threads:[~2005-07-01 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 15:12 MPC85xx DMA support for Kernel 2.6? Clemens Koller
2005-06-30 15:30 ` Kumar Gala
2005-06-30 15:56 ` Clemens Koller
2005-06-30 16:57 ` Murray.Jensen
2005-07-01 7:54 ` Clemens Koller
2005-07-01 8:36 ` Murray.Jensen
2005-07-01 13:59 ` Kumar Gala
2005-06-30 18:52 ` Dan Malek
2005-07-01 7:47 ` Clemens Koller
2005-07-01 14:02 ` Dan Malek [this message]
2005-07-01 14:15 ` Mark Chambers
2005-07-01 21:49 ` Dan Malek
2005-07-04 9:03 ` Clemens Koller
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=d946affc11510f7116710026d2a8d1f3@embeddededge.com \
--to=dan@embeddededge.com \
--cc=clemens.koller@anagramm.de \
--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).