From: Wolfgang Denk <wd@denx.de>
To: "Iñigo Lopez Barranco" <ilopez@albatros-sl.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: DMA support for MPC5xxx?
Date: Wed, 02 Jun 2004 17:08:07 +0200 [thread overview]
Message-ID: <20040602150812.DCA40C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 02 Jun 2004 16:35:32 +0200." <42A622EB18325843894BB8E1040E3DF5022732@sinaexchf>
In message <42A622EB18325843894BB8E1040E3DF5022732@sinaexchf> you wrote:
>
> Are MPC5200's IDE UDMA and MDMA have support with the latests changes in bestcomm?
Yes, partially :-(
> As I've read in the list, IDE and DMA were not supported due to bestcomm microcode (http://lists.linuxppc.org/linuxppc-embedded/200403/msg00214.html). Then, there is an announcement about a new API released on april 2004, included in linuxppc_2_4_devel
> cvs module. Does this solve the IDE DMA problem? I'm trying to use it on linuxppc_2_4_devel but doesn't work and I don't know if it's broken or I'm doing something wrong.
> BTW, the target is a Lite5200 board.
IDE DMA works if used alone, but it still causes conflicts when the
FEC ethernet driver is enabled, too. Motorola is investigating.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"It takes all sorts of in & out-door schooling to get adapted to my
kind of fooling" - R. Frost
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-02 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 14:35 DMA support for MPC5xxx? Iñigo Lopez Barranco
2004-06-02 15:08 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 10:50 Iñigo Lopez Barranco
2004-06-03 14:54 ` David Wolfe
2004-06-03 16:06 ` Matt Porter
2004-06-03 16:42 ` Wolfgang Denk
2004-06-03 18:33 ` Matt Porter
2004-06-03 18:50 ` Tom Rini
2004-06-03 20:19 ` Sylvain Munaut
2004-06-03 20:48 ` Matt Porter
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=20040602150812.DCA40C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=ilopez@albatros-sl.es \
--cc=linuxppc-dev@lists.linuxppc.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).