From: Stuart MENEFY <stuart.menefy@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: set_dma_addr missing ?
Date: Mon, 28 Jan 2008 14:00:55 +0000 [thread overview]
Message-ID: <479DE017.50702@st.com> (raw)
In-Reply-To: <38b2ab8a0801261302i68a84fdo6d6ebdb26d9acfc8@mail.gmail.com>
Francis
Francis Moreau wrote:
> On Jan 28, 2008 11:17 AM, Paul Mundt <lethal@linux-sh.org> wrote:
>> That's the plan, yes. DMABRG will probably need some special handling,
>> but that's pretty isolated. The ST40 DMACs will also prove to be a source
>> of irritation, so it's still going to take some iterations before
>> everything is happily migrated
>
> Sorry to be blind again but I can't find the current DMAC for the ST40...
I don't think there is much (if any) of it in the kernel.org trees
at the moment, have a look at the latest source release:
http://stlinux.com/pub/stlinux/2.3/updates/RPMS/host/stlinux23-host-kernel-source-sh4-2.6.23.13_stm23_0106-106.noarch.rpm
The FDMA stuff is all in drivers/stm (as in theory it should be shared
between a couple of architectures, in practice it isn't yet).
And yes, I know it is in need of a good clean up, sounds like moving
to the dmaengine API would be a good opportunity!
Stuart
next prev parent reply other threads:[~2008-01-28 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 21:02 set_dma_addr missing ? Francis Moreau
2008-01-28 2:47 ` Paul Mundt
2008-01-28 8:48 ` Francis Moreau
2008-01-28 9:09 ` Paul Mundt
2008-01-28 10:00 ` Francis Moreau
2008-01-28 10:17 ` Paul Mundt
2008-01-28 13:50 ` Francis Moreau
2008-01-28 14:00 ` Stuart MENEFY [this message]
2008-01-28 14:14 ` Paul Mundt
2008-01-28 14:28 ` Francis Moreau
2008-01-28 14:31 ` Francis Moreau
2008-01-28 14:40 ` Stuart MENEFY
2008-01-28 16:36 ` Francis Moreau
2008-01-29 0:44 ` Paul Mundt
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=479DE017.50702@st.com \
--to=stuart.menefy@st.com \
--cc=linux-sh@vger.kernel.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