From: Timur Tabi <timur@freescale.com>
To: Sebastian Siewior <linuxppc-embedded@ml.breakpoint.cc>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Using the loop feature of the DMA controller on MPC8544 DS
Date: Wed, 12 Mar 2008 13:47:30 -0500 [thread overview]
Message-ID: <47D82542.8020000@freescale.com> (raw)
In-Reply-To: <20080312172024.GB7255@Chamillionaire.breakpoint.cc>
Sebastian Siewior wrote:
> I need to hold src & dst each with one and two bytes makes four
> channels. And then I need one for normal transfers. So I guess I have to
> talk to my HW ppl that we have to change something :)
What kind of driver are you writing that needs four simultaneous DMA transfers?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-03-12 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 12:34 Using the loop feature of the DMA controller on MPC8544 DS Sebastian Siewior
2008-03-12 15:58 ` Timur Tabi
2008-03-12 17:20 ` Sebastian Siewior
2008-03-12 18:47 ` Timur Tabi [this message]
2008-03-12 20:44 ` Sebastian Siewior
2008-03-12 20:49 ` Timur Tabi
2008-03-12 21:15 ` Sebastian Siewior
2008-03-12 21:16 ` Timur Tabi
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=47D82542.8020000@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-embedded@ml.breakpoint.cc \
--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).